TestAssure Knowledge Base
< All Topics
Print

TestAssure Glossary

Action: A test case statement that is processed by TestAssure to perform an operation that is in the scope of testing. For example, actions can be used to overwrite Persona attributes, to assign shifts and input punches, and to specify the expected results. Every section of a test case (GIVEN, WHEN, THEN) requires at least one action.

Action Library: A library of all the predefined, automated actions that are available for test writing.

Activity Log: A tab in the Test Cases screen that tracks audit information such as edits made to a test case, or comments entered.

Functional Testing: Testing conducted to evaluate the compliance of a system with specified functional requirements. Functional Testing is designed to ensure a minimum level of software quality and is typically a precursor to further types of testing.

Given, When and Then: A test case is composed of three sections, GIVEN, WHEN, and THEN.

  • GIVEN: the preconditions of a test i.e., what is true before you start executing the steps of the test. The GIVEN is where the persona is specified, employees are scheduled, and the default Persona attributes are overwritten, such as the Hire Date.
  • WHEN: the steps to execute in which the GIVEN preconditions are modified, such as entering punches or pay code edits on the timecard.
  • THEN: the expected results of the test due to changes from the WHEN steps.

Parallel Testing: Testing conducted to compare the Customer’s current Timekeeping System and your new UKG solution. This type of testing helps you identify and respond to any behavioral differences between the two.

Performance Testing: Testing conducted to validate the application’s capabilities with respect to response time, stability, reliability, scalability, and resource usage.

Persona: A persona models the test employee that is created by TestAssure when running a test. The attributes for a persona in TestAssure are the same attributes that are used to setup an actual employee person in the WFM system. Examples of attributes are Hire Date, Organization Path, Pay Rule, etc. Every test case requires a persona as the subject of the test in the GIVEN section.

Regression Testing: Testing conducted as of a known good state in the WFM system to ensure recent updates or changes made to your UKG solution do create new issues and negatively affect previously working functionality. This type of testing is critical when deploying new releases, or when compliance and policy changes are made.

Symbolic Period: The timeframe in which the action should be processed. Examples of symbolic periods are Current Pay Period, Next Pay Period, Today, Current Week, etc.

Systems Integration Testing (SIT): Testing conducted to validate interactions between your UKG solution modules, include interoperability with other internal and external platforms and hardware. This type of testing ensures that all enterprise systems work together correctly. And it ensures that data moves accurately through your IT ecosystem and fully supports various business processes.

Test Builder: A feature in TestAssure to quickly generate tests of a predefined structure. Test Builder automatically populates the expected results based on the target environment’s configuration given a set of action parameters.

Test Library: A library of tests that help guide users on what tests to write, and how to write them.

Test Plan: A collection of tests in a Test Suite that are executed. A test case can belong to more than one test plan.

Test Suite: A collection of personas, tests, and test plans. Test Suites are used to organize tests in a logical manner or for a project purpose. For example, you may have a Test Suite to perform Functional Testing and another to perform User Acceptance Testing.

Test Target: The WFM environment that TestAssure should connect to when running tests.

User Acceptance Testing (UAT): Testing conducted to validate that end-to-end user workflows meet business requirements.

Unit Testing: Low-level tests designed to validate each individual configuration in isolation to ensure it functions as expected.

Scroll to Top