9 ms·
Just looked up what kinds of things we do on our CI & CD: - Run unit and casperjs/selenium UI tests - Minimize and optimize JS and CSS files if necessary - A
by aytekin 12y ago
Just looked up what kinds of things we do on our CI & CD:
- Run unit and casperjs/selenium UI tests
- Minimize and optimize JS and CSS files if necessary
- Add revision numbers to prevent caching on highly cached files
- Processing less files
- Closure compiler
- Grunt
- CDN cache clears or uploads
- Translation locale strings updates
- Deploying on servers
Tens of tasks/tests done in parallel and finished in 45 seconds.
The most important thing is by automating things, you are dramatically reducing possibility of making mistakes or forgetting something.
- rubiquity 12y ago> - Run unit and casperjs/selenium UI tests Of all of the steps you listed, this is the only step that actually pertains to CI. The rest are all part of deployment so they would fall under CD.
- aytekin 12y agoDon't agree. Except unit tests, the automated testing should be done on the very final version of the app/site/software, so that you can also catch integration/optimization related problems.