globalizejs/globalize

Performance tests

Open

#274 opened on Jun 10, 2014

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (645 forks)batch import
help wantednew feature

Repository metrics

Stars
 (4,759 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Goal

  • Test the performance impact of fixes/changes. So, we ensure our performance is continuously improved; #397
  • Compare the performance of Globalize vs. its competitors, so we ensure our performance is good compared to the market;

Workloads

  • TODO (should reflect what Globalize applications look like)

Implementation Ref: https://github.com/jquery/sizzle/tree/master/speed

Some other stuff to evaluate:

Contributor guide

Research direction
Implement performance benchmarks using a tool like benchmark.js, create test suites for key functionalities, compare with competitors, and automate via CI. Start by studying existing performance tests in similar projects (e.g., jQuery Sizzle) and then adapt to Globalize's codebase.
Tech stack
javascript
Domain
testingdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptGitBenchmarking concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40