Create GH Action Validation #3
Description
To mitigate the risk of introducing bug, we should add a GitHub Action that runs the code with a known input and output. That will allow for an automated validation. This would also help with issues such as #2.
To facilitate this, we may need to add a feature to write the found key to a file.
Test cases:
| Input | Pass Condition | Description |
|---|---|---|
| Bad Input | Found Key file is empty / non existent | Verifies we didn't accidently hard code the example output |
| Perfect Input | Found Key is correct | Verifies that the simplest use case works though it is highly unlikely this use case would happen in the wild. Also verifies that it actually tests the first possible key and doesn't pre-maturely rotates. |
| Good input that requires each key element to rotate at least once | Found Key is correct | Verifies that the rotation code works as expected |
| Good input that requires each key element to rotate multiple times | Found Key is correct | More rotation verification |
This ideally would also be tested against various versions of the driver and on both Windows and Linux.