22. January 2019 Miroslav Laššák

Good Testing

Testing, however, must involve verification of the functionality itself, and also verification that doing the procedure is part of the correct solution.

What is good testing?

The best quality is when every test case is covered by an automatic test, preferably when they are also independent of each other and can be run repeatedly.

Then it is possible to automatically retest all functionality after each change of code and detect any error when it is loaded into the code.
Why not do it that way when it’s so great? The problem is those two other factors, time and cost. Such full quality requires considerable amounts of effort, which means that the price of testing may be several times higher than the product development itself. Of course, there are also sectors where it is necessary to do this. But in the usual project there is always some compromise.

Testing is one of the means to improve quality. Improving quality necessarily results in higher costs and more time.

An opposite extreme is not to test at all.  This saves some and can even seem good sometimes, but only at the beginning. In the long run, this approach can lead to much greater costs.

Therefore, it is necessary to consider all the factors when testing and set the optimal levels of testing.

Proper testing is not just about quantity but also about the right moment. Tests should be done as soon as the design or code is changed, so any error is detected and corrected earlier.

The later an error is found, the more expensive it is to correct. For example, design errors are very difficult to remove at the end of the project, sometimes impossible.

Testing, however, must involve verification of the functionality itself, and also verification that doing the procedure is part of the correct solution.Whether the selected technologies meet the necessary criteria, for example on performance, whether the proposed solution is flexible enough for possible future enhancements, and so on.

The form, scope and test plan should be tailored for each custom project. We will be happy to advise you.

Every job requires the right tool.  Based on our experience, do not take a step without these types of helpers:

Test Management – XRay

Issue tracking – Jira

Modelling – EA (Enterprise Architecture)

CI (Continuous Integration) – Jenkins

Automatic testing

  • TestNG, JUnit
  • web – selenium
  • robots framework
  • cucumber

Performance testing – JMeter, Gatlink

What can we help you with?

  1. We will collect and analyze your testing requirements – what projects will be tested, how often, what are the release cycles, what is the structure of the test team, and so on
  2. We will develop a strategic test plan
  3. We’ll identify approaches to testing – Each project type has its own specifics and for each there are usually more types of approaches
  4. We’ll unify the testing approaches
  5. We help clients integrate with CI systems
  6. We will specify how to develop automatic tests
  7. We can install all necessary tools, or use our own installations and make them available to the customer
  8. We perform the testing itself – either automatic or by request, manually, with registration and evaluation, or with a link to the issue tracking system.


Miroslav Laššák


Similar projects

No similar projects