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

Temporary Suspension Order (TSO)

An order issued by the Deputy Director for CCLD which suspends a license prior to a hearing. Temporary suspension orders are issued when imminent danger exists, to protect residents or clients of a facility from physical or mental abuse, abandonment, or any other substantial threat to health or safety.

Termination of Parental Rights

The process of involuntarily taking away the parental rights of a parent that has abandoned a child, has without just cause failed to support a child, has neglected or abused a child, has stood by and allowed others to neglect or abuse a child, or who because of extended incarceration in prison, will be unavailable to properly parent or nurture the child during its formative years. Once the parental rights of both parents of a child have been severed, the child will become available for adoption by another family. See California W&IC 366.26

Testable Increment (TI )

A Testable Increment spans multiple 3-week sprints and may bundle together Building Blocks from multiple process/subject areas (e.g. Investigations, Case Management, Courts, Eligibility and Resource Management). A given Testable Increment (or series of Testable Increments) may deliver a specific scenario corresponding to a distinct child/family pathway through one or more Building Blocks.

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.