regulators: Fix 'run_rule' and 'set_device' test cases fail.
Fix test case failures for the 'run_rule' and 'set_device' actions.
The failures are caused by new logic in the validator that checks for invalid rule IDs and device IDs.
Signed-off-by: Bob King <Bob_King@wistron.com>
Change-Id: I764bd101d0ef635375d13b2921a292799ff1ada9
diff --git a/phosphor-regulators/test/validate-regulators-config_tests.cpp b/phosphor-regulators/test/validate-regulators-config_tests.cpp
index 2191db1..6960462 100644
--- a/phosphor-regulators/test/validate-regulators-config_tests.cpp
+++ b/phosphor-regulators/test/validate-regulators-config_tests.cpp
@@ -2206,7 +2206,7 @@
TEST(ValidateRegulatorsConfigTest, RunRule)
{
json runRuleFile = validConfigFile;
- runRuleFile["rules"][0]["actions"][1]["run_rule"] = "set_voltage_rule1";
+ runRuleFile["rules"][0]["actions"][1]["run_rule"] = "read_sensors_rule";
// Valid: test run_rule.
{
json configFile = runRuleFile;
@@ -2329,7 +2329,7 @@
TEST(ValidateRegulatorsConfigTest, SetDevice)
{
json setDeviceFile = validConfigFile;
- setDeviceFile["rules"][0]["actions"][1]["set_device"] = "io_expander2";
+ setDeviceFile["rules"][0]["actions"][1]["set_device"] = "vdd_regulator";
// Valid: test set_device.
{
json configFile = setDeviceFile;