Feature #6695
closed
Bridge needs basic functional tests
Added by Evgeny Novikov about 8 years ago.
Updated almost 8 years ago.
Published in build:
040582c
Description
Bridge is the only Klever component that has an access to a database, thus it has to always behave correctly. The only way to ensure this somehow is to develop and automatically run a plenty of tests.
- Priority changed from Normal to Urgent
An initial set of tests should include at least some tests for all basic functions like registration of users, changing of user profiles, viewing jobs, reports and marks, creating/updating jobs and marks, downloading/uploading archives of jobs and marks.
More advanced tests can include checks of various user rights for performing various operations, performance tracking, more different cases briefly covered in the initial set of tests, in particular, stress tests, proper visualization of error traces and so on.
- Subject changed from Bridge needs tests to Bridge needs basic functional tests
- Status changed from New to Resolved
- % Done changed from 0 to 100
An initial set of tests is in the branch "testing".
- Status changed from Resolved to Closed
- Published in build set to 040582c
Great! I merged the branch to master in 040582c.
In addition to tests themselves there are several small improvements in implementation.
There are instructions how to test Klever Bridge in the developer documentation.
Also available in: Atom
PDF