Improvements to testing suite and practices
complete
Deniz DUX
Goal
Making our testing and QA processes cover as much surface area as possible, in order to prevent bugs and vulnerabilities on our production environments.
Context
DUX team has concluded that our current QA/testing process... sucks. We do some manual testing but this does not nearly cover enough surface area for bugs and vulnerabilities (eg. edge cases, business logic, on-chain calamities).
Initial To-Do's
Verify that all critical paths/user flows are defined
Determine whether all these critical paths are covered by an integration test—write down findings in the working document
Evaluate naming convention of the integration tests and suggest improvements to make it more coherent/consistent
Create tickets for adding/improving integration tests
Future steps
Evaluate test coverage of back-end processes and components
Evaluate Spock tests (refer to Tyler's prior work)
Improve process: Make sure ALL PRs with new code include integration tests—developers should keep each other sharp on this.
Improve process: For any new bugs we catch, the fix should also include a new test that would cover similar bugs.
Consider how to improve our manual testing process
Stay in tune with developments at Chaos Labs for simulating on-chain edge cases (testchain)
Deniz DUX
complete
Marking this as complete since release v0.3.0 which features a new e2e integration testing suite. Currently we are collaborating with the TechOps Core Unit to iteratively improve our testing setup by adding new types of tests & monitoring, increasing code coverage and making improvements/optimisations to the govportal code to make tests run more reliably.
Deniz DUX
Update: We have migrated our testing setup from Kovan to Görli testnet. In addition we have been working on a solution to reduce overhead of generating the required testnet states for proper testing. We have also automated various tests and have been working on new tests for the Dai.js library. DUX team will release a full write-up of the improvements once we are satisfied with the current iteration of our testing & QA process.
Deniz DUX
in progress