Implement new set of system tests
Categories
(Tecken :: General, task, P2)
Tracking
(Not tracked)
People
(Reporter: sven, Assigned: sven)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
Attachments
(4 files)
The current "system tests" for Tecken test interesting aspects of the public API, but they are not very systematic or complete. The codebase is also a bit hard to extend, since the tests are written as a set of interacting standalone scripts that invoke each other.
To get a more complete, systematic and maintainable set of system tests, we would like to start from scratch using pytest as the test framework. pytest provides a lot of flexibility when running the tests, and has built-in result reporting, so we can focus on writing the actual tests.
We plan to rename the old systemtests
directory in the Tecken repository to smoketests
, or alternatively to split them out to a separate repository.
We will need a bit of infrastructure to get going:
- A wrapper script to conveniently run the tests.
- A Tecken client implementation supporting Tecken's complete public API, including retry behaviour for 500s and 429s.
- Example symbol files and zip archives stored in a publicly available place, e.g. a GCS bucket, so we can test the upload-by-download functionality with a sufficiently big file.
- A way to generate fake symbol files and zip archives on the fly.
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Comment 1•8 months ago
|
||
Assignee | ||
Comment 2•8 months ago
|
||
Assignee | ||
Comment 3•8 months ago
|
||
Assignee | ||
Comment 4•8 months ago
|
||
Assignee | ||
Comment 5•8 months ago
|
||
Comment 6•7 months ago
|
||
Assignee | ||
Comment 7•6 months ago
|
||
Assignee | ||
Comment 8•6 months ago
|
||
Comment 9•5 months ago
|
||
Everything up to this point was deployed to prod in bug #1922112 just now. Tagging Sven to verify.
Assignee | ||
Comment 10•5 months ago
|
||
The changes so far either affected the new GCS environment or the new systemtest directory in the tecken repo. Neither affect the AWS deployment, so there's nothing to verify.
Description
•