Refactor watchdog test case (New)

[LiaoU3]

Description

After refactoring watchdog test cases, there are several benefits and flexibility.

1. Fit all classic and core, oem or stock image.
2. Automatically set watchdog timeout

The only prerequisite is to set up the environment variable before starting the test.

• WATCHDOG_TYPE=wdat_wdt
• WATCHDOG_IDENTITY=wdat_wdt

Resolved issues

N/A

Documentation

N/A

Tests

• Before setting environment variables: https://certification.canonical.com/hardware/202311-32337/submission/362459/
• After setting environment variables: https://certification.canonical.com/hardware/202311-32337/submission/362460/

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 43.12%. Comparing base (2ee5cc4) to head (a44a16d).
Report is 65 commits behind head on main.

❗ Current head a44a16d differs from pull request most recent head 760d798

Please upload reports for the commit 760d798 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1125      +/-   ##
==========================================
- Coverage   43.21%   43.12%   -0.09%     
==========================================
  Files         356      352       -4     
  Lines       38662    38543     -119     
  Branches     6561     6555       -6     
==========================================
- Hits        16706    16620      -86     
+ Misses      21293    21257      -36     
- Partials      663      666       +3     

Flag	Coverage Δ
provider-base	16.12% <100.00%> (-0.18%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[fernando79513]

The watchdog_config_test.py seems to be defined twice, both in providers/base/bin and providers/base/tests

[LiaoU3]

The watchdog_config_test.py seems to be defined twice, both in providers/base/bin and providers/base/tests

Thank you. Removed!

[Hook25]

Please split the PR into two (pxus are a followup to python)!

Gave some inline feedback here and there

[LiaoU3]

Latest submission: https://certification.canonical.com/hardware/202306-31658/submission/367954/

[LiaoU3]

I will rewrite the unittest when this is being considered an approved PR.

[Hook25]

Some comments here and there, only major thing is the detect function that can't work if there is more than 1 watchdog. Its unclear to me what to do in this situation, especially if there is more than 1 watchdog kind. I have proposed a patch to the function, but we should consider what to actually do in this situation, because this may not be what we want

[LiaoU3]

@Hook25 Please see my comment.

[LiaoU3]

@Hook25 I notice that in my jobs I require some environment variables like WATCHDOG_TYPE and
WATCHDOG_IDENTITY, however, the machines in the sru pool has not been configured those variables, as a result, it may break the sru testing.
Do you have any idea how we can prevent from this?