View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008558 | CTT UA Scripts | 1 - Script Issue | public | 2023-01-03 14:07 | 2023-02-18 22:48 |
| Reporter | Alexander Allmendinger | Assigned To | Archie Miller | ||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.03.501 | ||||
| Target Version | 1.03.502 | Fixed in Version | 1.03.502 | ||
| Summary | 0008558: A and C Refresh stops without running all test scripts and indication of it | ||||
| Description | When the device clock and the CTT clock are not well synchronized, the execution of the tests in this CU is stopped. In this case only the error "Unable to get start and stop events" is displayed and further test cases are not run and therefore not displayed. Whenever the execution of tests in a CU is aborted, a proper error message indicating the stop of the CU test run needs to be printed to clearly describe that some test cases have not been run. | ||||
| Tags | No tags attached. | ||||
| Files Affected | /maintree/Alarms and Conditions/A and C Base/Refresh/Test Cases/initialize.js | ||||
| related to | 0008565 | closed | Archie Miller | A&C scripts printing misleading skip messages or marking tests as passed which are not run |
| related to | 0008559 | closed | Archie Miller | A and C Refresh stops when time shift between CTT and SUT is bigger 0ms |
|
|
The CTT time and Device Time should have no influence on test execution - all tests should just be looking at the Device time. CTT time is only for how long to run testing and this should be a larger number and if it is encountered it is reported as a problem. test should only stop when all tests have been covered. |
|
|
Resolved synchronization issues |
|
|
reviewed changes agreed to changes, closed issue |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-03 14:07 | Alexander Allmendinger | New Issue | |
| 2023-01-03 18:21 | Paul Hunkar | Description Updated | |
| 2023-01-03 18:41 | Paul Hunkar | Note Added: 0018400 | |
| 2023-02-06 15:21 | Paul Hunkar | Assigned To | => Archie Miller |
| 2023-02-06 15:21 | Paul Hunkar | Status | new => assigned |
| 2023-02-06 23:46 | Archie Miller | Relationship added | related to 0008559 |
| 2023-02-06 23:47 | Archie Miller | Relationship added | related to 0008565 |
| 2023-02-07 00:30 | Archie Miller | Status | assigned => resolved |
| 2023-02-07 00:30 | Archie Miller | Resolution | open => fixed |
| 2023-02-07 00:30 | Archie Miller | Note Added: 0018670 | |
| 2023-02-07 00:31 | Archie Miller | Files Affected |
=> /maintree/Alarms and Conditions/A and C Base/Refresh/Test Cases/initialize.js
/maintree/Alarms and Conditions/A and C Base/Refresh/Test Cases/initialize2.js /maintree/Alarms and Conditions/A and C Base/Refresh/Test Cases/Test_001.js /maintree/Alarms... |
| 2023-02-18 22:48 | Paul Hunkar | Fixed in Version | => 1.03.502 |
| 2023-02-18 22:48 | Paul Hunkar | Target Version | => 1.03.502 |
| 2023-02-18 22:48 | Paul Hunkar | Status | resolved => closed |
| 2023-02-18 22:48 | Paul Hunkar | Note Added: 0018766 |
