Task #146
openoptimize webapp tests
0%
Description
(venv) user@workstation:~/Code/catchlist_todo/test/webapp$ rm -r reports/lelda && time pytest tests/tasks/test_task_components.py --env=local --headless=True --alluredir="./reports/lelda"
...
collected 20 items
tests/tasks/test_task_components.py .................... [100%]
==================================================== 20 passed in 279.10s (0:04:39) ===========================================
real 4m39.560s
user 0m24.739s
sys 0m8.290s
4.6 minutes for 20 tests isn't a great runtime. The API suite has ~800 tests so we absolutely need to speed this framework up before building a bunch of tests, or else we'll just have a glut of tests that never get run.
per ticket #145 we can parallelize tests, but probably only when running them locally.
There's almost certainly a lot of fat to cut off of the framework, as it's pretty newly established.
Updated by Sam Pearson 2 months ago
- Target version set to V2.2 - Webapp Component Demos
putting this in the webapp component demo version; if we're going to do anything structural/global to the test framework it's best to do that before we build a bunch of tests.
Updated by Sam Pearson 24 days ago
- Priority changed from Normal to Low
Bumping this down to low priority because end-to-end webapp tests are at the very peak of the "test pyramid" - there should be a ton of unit tests, fewer component tests, fewer e2e api tests, and even fewer e2e webapp tests. Webapp tests are necessarily slow and brittle, so we shouldn't ever have a battery of 800 of them.
Still, 5 minutes for a run of 20 tests isn't great, and we should optimize.
Updated by Sam Pearson 23 days ago
- Engineering Effort set to unknown
- App Component set to Webapp Testing
Unknown effort, probably large or XL including figuring out how to optimize.