CWDS Glossary
The CWDS Glossary includes a List of Acronyms and defined terms captured from various models, reports, and other artifacts pertaining to the Child Welfare System – California Automated Response and Engagement System (CWS-CARES) Project. The Glossary standardizes terms used across the various project disciplines; each term is defined with its meaning specific to the project domain.
The State may update the CWDS Glossary at any time. Any questions please contact CWDS Communications.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Test Automation
Business Definition: This is a term used in software quality assurance, used to describe a script that runs a repeatable, unopinionated test.
Technical Definition: The use of software separate from the software being tested to control the execution of tests and the comparison of actual outcomes with predicted outcomes. Test automation can automate some repetitive but necessary tasks in a formalized testing process already in place or perform additional testing that would be difficult to do manually. Test automation is critical for continuous delivery and continuous testing.
Test Bed
The test execution environment configured for testing. Test bed consists of specific hardware, software, Operating system, network configuration, the product under test, other system software and application software.
Test Case
A test artifact developed for a particular test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.
Test Cycle
An ordered list of test cases assigned to testers and test environments created to achieve specific testing goals (usually a longer test run, such as regression tests, build verification tests, end-to-end tests, etc.).
Test Environment
A test environment is an attribute of a test execution result used to determine the environments to be tested for each test case. Planning your test environment includes defining your platform coverage, such as operational systems, browsers, databases, etc.
Test Execution Result
A set of information that generates and is stored when a test case is executed. Data includes the tester responsible for the execution, the execution date, the defects raised, the environment and the status of the execution (e.g., passed or failed), and more.
Test Library
The location where test cases are created and stored. This is also known as a test repository. Any Jira project can be a test library. Test cases are created and managed under a test library; however, you can share and reuse test cases across Jira projects when necessary to prevent duplication and increase reusability.
Within a test Library, you can organize test cases by using a folder structure and categories by using labels or custom fields.
Test Plan
An artifact used to track testing progress throughout an entire release or version. You can associate several test cycles to a test plan to get real-time progress reports. Test plan fields are customizable, which allows you to track scope, risks, strategy, entry and exit criteria, test environment, test bed, and more.
Test Script
A specified sequence of steps and expected results for the execution of a test case. This is also known as manual test script or test procedure specification. Test Management for Jira allows the use of traditional step-by-step as well as BDD (Gherkin syntax) and plain text scripts.
Therapeutic Foster Care (TFC)
A licensed foster care facility or certified home of a foster family agency that is licensed to provide Residential Behavioral Management services. TFCs serve children and youths who have special psychological, social, behavioral, and emotional needs which require more intensive or therapeutic services than are found in traditional foster care.