Glossary
Term | Definition |
|---|---|
Unit test | All external calls are virtualized so that you are executing a test case for a program in isolation. All external calls (Files, Db2, sub-programs CICS/IMS APIs) are virtualized/ stubbed out by the test case. |
Functional test | Executing a test case for a program in a live environment with live data. |
Integration test | Executing a test case that tests collaboration between two or more programs in a live environment with live data. |
Virtualized | Executing a test case for a program in isolation. |
Non-virtualized | Executing a test case in a live environment with live data. |
Shift Left | A testing scenario in which testing is done earlier in the software development life cycle. |
Test-driven development | A testing scenario in which you have test cases for all software requirements. |
Positive Testing | A type of testing which is used in in which the program gets valid input and returns valid output—the normal successful execution. |
Negative Testing | A type of testing in which negative test cases are created for failure pathways in a program. This also includes test cases where invalid data is sent to the program to verify if it abends correctly or returns a specific error code. |
Boundary Testing | A type of testing which is used to test values at the high and low boundaries in a program. |
Date/Time Testing | A type of testing in which pieces of code get processed on specific dates and times. |
Regression Testing | A type of testing which ensures that previously developed and tested software continues to work in the same way after code changes have been made or after it has interfaced with other software. |
Baseline/rebaseline Testing | A type of testing in which you create test cases for a program that works which act as the baseline tests for a program. These baseline tests are run before making code changes to ensure that the current system works as expected. |
Test cases | A set of actions that are executed to test a specific piece of code or functionality in a program. |
Repository | A place to store code, or software projects. |
Project | A project contains all of the files needed for testing. |
Test scenario | Test scenarios are used to define and describe what to test, which input to use, and which output to expect in order to consider the test successful. |
Test suite | Test suites enable you to execute multiple test scenarios in one test run. |
Pipeline | A set of automated processes and tools that help developers and operations to collaborate on building and deploying code. |
Automated pipeline | A DevOps pipeline is used to automatically test, build and/or deploy changes. They are typically called Continuous Integration/ Continuous Delivery/Deployment (CI/CD) pipelines since they either automatically build or deploy code when needed. |
SCM | A Source Control Management (SCM) system enables developers and testers to collaborate and manage test cases for different versions of the programs they are testing. |
Code Coverage | Code coverage identifies the gaps in testing and helps determine if additional test cases are required. |