refactor(anta.tests): Nicer result failure messages hardware test module

[geetanjalimanegslab]

Nicer result failure messages for following test module.

1. Hardware

Note: Test with the Unit tests only, not able to test on ATD lab.

Fixes #587

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have run pre-commit for code linting and typing (pre-commit run)
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes (tox -e testenv)

[codspeed-hq]

CodSpeed Performance Report

Merging #1044 will not alter performance

_{Comparing geetanjalimanegslab:fix_hardware_module_failure_msg (dccc1aa) with main (7c9bef4)}

Summary

✅ 22 untouched benchmarks

[carl-baillargeon]

Hardware State, does that mean temperature range like it was previously mentionned? I feel like it is not the same.

[geetanjalimanegslab]

Hi @carl-baillargeon ,
Here , We are validating the same parameter as earlier validation {'hwStatus': 'ko', 'alertCount': 0}}
I have divided this check into two separate messages.,

1. Check for 'hwStatus': 'ok' am updating it as
Sensor: DomTemperatureSensor54 - Invalid Hardware State - Expected: ok Actual: ko

1. Check for 'alertCount': 0' am updating it as
Sensor: DomTemperatureSensor54 - Non-zero alert counter - Actual: 1
Can you please guide me here? Do we need to update the message or validation?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud