Introduction to Software Testing Coursera

Overview

You will have actively created test cases and run them using an automated testing tool. You will being writing and recognizing good test cases, including input data and expected outcomes. This Introduction to Software Testing course offered by Coursera in partnership with University of Minnesota is part of the Software Testing and Automation Specialization.

After completing this course, you will be able to:

• Describe the difference between verification and validation.

• Explain the goal of testing.

• Use appropriate test terminology in communication; specifically: test fixture, logical test case, concrete test case, test script, test oracle, and fault.

• Describe the motivations for white and black box testing.

• Compare and contrast test-first and test-last development techniques.

• Measure test adequacy using statement and branch coverage.

• Reason about the causes and acceptability of and poor coverage

• Assess the fault-finding effectiveness of a functional test suite using mutation testing.

• Critique black-box and white-box testing, describing the benefits and use of each within the greater development effort.

• Distinguish among the expected-value (true), heuristic, consistency (as used in A/B regression), and probability test oracles and select the one best-suited to the testing objective.

• Craft unit and integration test cases to detect defects within code and automate these tests using JUnit.  To achieve this, students will employ test doubles to support their tests, including stubs (for state verification) and mocks.

Key facts

• This course is primarily aimed at those learners interested in any of the following roles: Software Engineer, Software Engineer in Test, Test Automation Engineer, DevOps Engineer, Software Developer, Programmer, Computer Enthusiast. 

• We expect that you should have an understanding of the Java programming language (or any similar object-oriented language and the ability to pick up Java syntax quickly) and some knowledge of the Software Development Lifecycle.