Details
-
Story
-
Resolution: Done
-
High
-
2.2.2
-
[2.5] - Sprint 2
-
1
Description
At this point, it takes about 2 and a half hours for all automatic tests to be performed. We need to investigate the ways to shorten this time. Possible solutions:
- adding tags to test scenarios and limit the amount performed with every PR
- introducing performing tests in many threads
- maybe some another way
We need to find the best compromise between tests duration and tests scope.
At first, in this story, we'll take care the page-builder non-PR builds (triggered every night and by merge). Then, we'll do the follow-up for other less-travis-blocking repos.
Attachments
Issue Links
- relates to
-
EZP-30098 [Travis] Implement solution for running tests in threads based on fastest
- Closed