Overview
Page Objects (POs) and test cases maintain separate audit logs. When a Page Object is modified, these changes are recorded exclusively in the audit log for that specific PO. These updates will not appear in the audit logs of the test cases that use the PO. This is the expected system behavior.
How It Works
Test cases are designed to consume or call Page Objects. The test case itself does not contain the PO's steps, but rather a reference to the PO. The logging mechanism is separated based on where the edit occurs.
- Page Object Edits: Any modification, such as adding, deleting, or changing steps within a PO, is logged in the audit history of that specific Page Object.
- Test Case Edits: Changes made directly to a test case, like reordering steps or adding new actions that are not part of a PO, are logged in that test case's audit history.
- Separation of Logs: Because editing a PO is not a direct change to the test case that calls it, the test case's audit log remains unchanged. The test case simply uses the current version of the PO during execution.
Viewing a Complete Change History
To get a comprehensive view of all changes that could affect a test's execution, you must review the audit logs for both the test case itself and any associated Page Objects it uses.
Related Information
- Creating Page Objects
- Editing Page Objects
- Using the Log Views