How We Test

Context-Driven Testing

Each project is unique, and our goal is to serve it well. To achieve it, we have to understand the project, you as its stakeholder, and your interests. We examine these details and carefully choose the most effective and suitable testing practices for the project. We consider your own definitions of product quality as well as your deadlines and budget, doing the best we can to satisfy your expectations.

Test Planning

Rather than trying to apply a single "best practice", we accept that very different practices will work best under different circumstances. So our test planning includes far more than just creating test cases. We use test design techniques to achieve broader test coverage with less effort and create the most appropriate test documentation, which may include test cases, checklists, workflow diagrams, combinatorial tables, and others. These instruments help us to impress our clients by the actual process of testing rather than just paperwork.

Test Automation

We are sure that testing benefits from using various tools including automated UI and API checks. In the hands of an experienced QA engineer, automation may speed up detection of issues, provide solid test coverage and leave space for more thorough and sophisticated manual testing.

Rapid Testing

Under normal conditions, we skilfully design the testing and consistently perform it by the plan. When there's a need to test a product immediately, under conditions of uncertainty, we proceed with confidence, applying our mindset and skill to solve testing problems under pressure. In any way, you will perceive that our time is well spent, and therefore rapid.

scroll top