Quality Assurance & Testing
Automated tests and a second pair of eyes on everything that reaches the main branch.
- Automated
- Review
- CI
How it works
Testing is not a stage before delivery but part of every working day.
What gets checked automatically
Business rules are checked where they live — in the backend, individually and fast. The paths the business depends on are checked end to end: sign in, create a record, complete it, find it again. These run on every change, not on request.
What we deliberately do not automate
Automating everything does not pay. Tests that break with every visual change cost more than they find. We automate what is stable and consequential, and check the rest by hand.
Review
Nothing reaches the main branch without a second person having read it. That finds bugs, and it means more than one person understands how the system works. In the long run the second point matters more.
Your acceptance
We test against the acceptance criteria. You test against reality — whether the process really runs that way in your organisation. Both are needed, and neither substitutes for the other.
- The acceptance criteria from requirements engineering — they are the template for the tests.
- Someone on your side for subject-matter acceptance. We check that it works; you check that it is right.
- Test data that resembles reality. Tidy sample data uncovers no bugs.
A test suite that runs on every change, and a main branch that is deployable at any time.
If you skip this
Without tests, every change is a risk to everything that already exists. The effect does not show in month one but in month eight: development slows down because nobody dares touch anything without clicking through the whole app by hand.
Questions about this step?
A conversation costs nothing and takes half an hour. Afterwards you will know whether we are a fit.