Closed GregDomzalski closed 1 month ago
2 files 2 suites 2s :stopwatch: 3 616 tests 3 616 :white_check_mark: 0 :zzz: 0 :x: 3 618 runs 3 618 :white_check_mark: 0 :zzz: 0 :x:
Results for commit c93f6871.
2 files 2 suites 5s :stopwatch: 3 608 tests 3 608 :white_check_mark: 0 :zzz: 0 :x: 3 610 runs 3 610 :white_check_mark: 0 :zzz: 0 :x:
Results for commit c93f6871.
Package | Line Rate | Branch Rate | Complexity | Health |
---|---|---|---|---|
Yubico.Core | 42% | 31% | 4257 | ➖ |
Yubico.YubiKey | 51% | 47% | 18549 | ➖ |
Summary | 49% (31645 / 64503) | 44% (8041 / 18093) | 22806 | ➖ |
Minimum allowed line rate is 40%
2 files 2 suites 3s :stopwatch: 3 608 tests 3 608 :white_check_mark: 0 :zzz: 0 :x: 3 610 runs 3 610 :white_check_mark: 0 :zzz: 0 :x:
Results for commit c93f6871.
Description
The YubiKey allows a caller to temporarily adjust the touch threshold which affects the sensitivity of the capacitive touch sensor. It is possible to raise the threshold (thus making the key less sensitive) and more difficult for the touch sensor to activate. This is interesting in automation scenarios where the YubiKey may be in some sort of configuration or test harness. We have found in our own testing that being able to raise the threshold from 6 to about 8 or 9 is able to improve the reliability of our touch automation quite substantially. I am aware of other organizations who have mechanically automated provisioning, so this may prove useful for them too.
Fixes # (internal: PROD1942)
Type of change
Please delete options that are not relevant.
How has this been tested?
Through updating the test app and verifying that the set command succeeds.
Test configuration:
Checklist:
dotnet format
to format my code