Get up to 80 % extra points for free! More info:

Lesson 11 - Java Testing - Quality Assurance, CAN PIG RIDE, and ISTQB

In the previous lesson, Java Testing - Acceptance Tests of Real Applications II, we showed sample codes of acceptance tests from real-world commercial applications. At the very beginning of the course, we explained the reason why to write tests at the first place, what kind of tests there are and what extra value they mean to us. My goal was to motivate you to test your applications and give you a competitive advantage over development teams managed by someone who doesn't understand software development (in practice, managers with just economic education, unfortunately, often manage such teams).

Until now, we have been very practical. But there are still some theories and terminology around testing that we should know and you're probably going to encounter it in your business. These are best practices, well-known documents, standards, and procedures. We also haven't mentioned the user interface testing. In the next two lessons, we're going to introduce this information to make your knowledge set complete. At the end of the course, we'll also try to stress test our Java application.


SLA – Service Level Agreement

Service Level Agreement (SLA) is usually one of the documents between the software supplier (us) and the customer. Here we define how the software should work, how we guarantee it, and how flexible we intend to respond to events of downtime and failures in general. The bigger the project and the more money it cost, the more money is blown up when it stops working and the more pressure there will be on you putting it back into operation.

It always makes sense to define the SLA, no matter it's just a template e-shop for thousands or a government funded application for millions. Defines at least what you're responsible for, in what time-frame you're willing to fix errors (for example, 2 years since the delivery), and how much money you'll add new features for. Because the customer doesn't understand IT, they think, that


...End of the preview...
Continue further

You will gain knowledge worth hundreds of thousands for a few crowns

You've come here and that's great! We believe that the first lessons showed you something new and useful
Do you want to continue the course? Go to the premium section.

Buy this course

Buy all currently available lessons with exercise submitting and other features for just $21.60
Current account balance $0
By buying this package, you'll have access to all 12 articles (12 lessons) in this course.

This article is licensed: Premium III, by buying this article, you agree with the terms of use.

What will you get from us in the next lessons?
  • Unlimited and permanent access to individual lessons.
  • High quality IT knowledge.
  • Skills to help you get your dream and well-paid job.

Article description

Requested article covers this content:

In this Java tutorial about testing web apps, we'll explain terms such as SLA, QA, SQA, go through CAN PIG RIDE and ISTQB practices (pesticides paradox).

You gain credits by supporting our network. This is done by sending a helpful amount of money to support the site, or by creating content for the network.

Article has been written for you by David Capka Hartinger
The author is a programmer, who likes web technologies and being the lead/chief article writer at He shares his knowledge with the community and is always looking to improve. He believes that anyone can do what they set their mind to.
Unicorn university David learned IT at the Unicorn University - a prestigious college providing education on IT and economics.