ember-cli / ember-cli/stress-app

plan to for tracking data

Open
#3 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
9
Forks
4
PR merge metrics
No merged PRs in 30d

Description

So its important for us to track/log improvements in some way.

As the app will likely keep changing. This might be tricky, but worth a shot anways. In theory if we stick to stable features we can go replay the app against different versions of existing deps.

We should also be sure to track times of vanilla apps. We don't want normal apps to suffer.

We should likely test the following flows:
1. ember cli startuptime (no build)
2. ember build
3. 2. ember build --env production
4. ember s
5. incremental changes during serve
- touch app/app.js
- touch tests/..
- touch bower_components/...

And finally, test this on windows/osx/linux when possible.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.