Automated Software Testing: Model and State-based Testing

Software testing gets a bad rap for being difficult, time-consuming, redundant, and above all - boring. But in fact, it is a proven way to ensure that your software will work flawlessly and can meet release schedules.

In a two-course series, we will teach you automated software testing in an inspiring way. We will show you that testing is not as daunting a task as you might think, and how automated testing will make you a better developer who programs excellent software.

This second course builds upon the first course's material. It covers more advanced tools and techniques and their applications. Key topics include state-based and web testing, combinatorial testing, mutation testing, and property-based testing.

This is a highly practical course. Throughout the lessons, you will test various programs by means of different techniques. By the end, you will be able to choose the best testing strategies for different projects..

If you are or want to become a five-star software developer, QA engineer, or software tester, join this course. Testing will never be the same again!

Topic 1: Model-based testing and decision tables

• Create decision tables to represent complex decisions of your software.
• Apply different coverage criteria in the decision table to generate test cases.

Topic 2: Model-Based testing and state machines

• Devise state machines that represent the software system (e.g., web systems) and use them to generate test cases.
• Apply different coverage criteria to generate test cases that cover different paths of the system.

Topic 3: Self-testing

• Understand what pre-conditions, post-conditions, and invariants are, and how to design them in your software system.

• Use these contracts to test your software from the “inside out”

• Write properties and let property-based testing frameworks generate test cases automatically.

Topic 4: Mutation testing

• Understand the key ideas behind mutation testing.
• Apply mutation testing in software systems and discover what parts of your software are not tested enough.