We are a company dedicated to quality, efficiency and excellence in both: our team, and the software subject to our review. We make it our point to achieve these goals by means not yet deemed entirely conventional in most of the community. We take offence to QA engineers being regarded as mere click monkeys, and aim to break such stereotypes. To that end, we provide you with motivated, experienced and most of all capable engineers to bolster your software development team, and improve your software development process from start to finish. For that reason, we are not content with merely receiving an end product from the development team, and running our test against it; no, we aim to be actively involved as early as the requirement phase, then throughout the entire process – all the way to production maintenance. Such an approach will ensure superior software, but also minimize your software development costs by identifying defects in early stages of development.

Our mission: to achieve excellence in software by means of challenging common software development misconceptions.

Such misconceptions include:

  • Great developers write bug-free code: even the best of software will inevitably have defects, and there has never been an operational application that did not contain any errors. Admittedly, even including the best QA will not make your application bug-free, but it will ensure your application is stable, functional and will keep the inevitable defects marginal.
  • Developers are not able to test their own stuff: no, developers are not able to test their own stuff! At least not sufficiently. Developers are often under pressure from overbooking and strict deadlines, and in such situations, proper dev testing is the first thing to go. You don’t want to have a surgeon, no matter how capable, fixing your car. It’s always better to call in a professional.
  • Requirements are written in stone: wrong again, requirements do need to be challenged, and challenged hard. Identifying potential issues in the requirement phase is the least costly option. After an incorrect/ incomplete requirement moves out to development, and even reaches the testing phase – the cost multiplies.

QA is just for testing: we tend to disagree. Testing is just one aspect of our work. In order to fulfill its full potential QA must co-author requirements, review code, design test plans, design test, execute testing, sign-off on releases, support production, and more…