Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit a1477d0

Browse files
committed
Add note about duration recordings to parity testing readme
1 parent 8f77959 commit a1477d0

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

‎docs/testing/parity-testing/README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -248,3 +248,12 @@ localstack.testing.snapshots.transformer: Replacing regex '000000000000' with '1
248248
localstack.testing.snapshots.transformer: Replacing regex 'us-east-1' with '<region>'
249249
localstack.testing.snapshots.transformer: Replacing '1ad533b5-ac54-4354-a273-3ea885f0d59d' in snapshot with '<uuid:1>'
250250
```
251+
252+
### Test duration recording
253+
254+
When a test runs successfully against AWS, its last validation date and duration are recorded in a corresponding ***.validation.json** file.
255+
The validation date is recorded precisely, while test durations can vary between runs.
256+
For example, test setup time may differ depending on whether a test runs in isolation or as part of a class test suite with class-level fixtures.
257+
The recorded durations should be treated as approximate indicators of test execution time rather than precise measurements.
258+
The goal of duration recording is to give _an idea_ about execution times.
259+
If no duration is present in the validation file, it means the test has not been re-validated against AWS since duration recording was implemented.

0 commit comments

Comments
 (0)