Actions
Bug #17358
closedBug #17348: when importing a technique with /api/internal/techniques, the order of parameters is not respected
ncf method write test in error
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
Tests report:
Tests run: 16, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.201 sec <<< FAILURE! Preparing files for technique Test Technique created through Rudder API should::Should generate expected metadata content for our technique(com.normation.rudder.ncf.TestTechniqueWriter) Time elapsed: 0.004 sec <<< FAILURE! java.lang.Exception: /tmp/test-technique-writer-2020-05-07T18:39:42.119+02:00/techniques/ncf_techniques/technique_by_Rudder/1.0/metadata.xml is not the same as src/test/resources/configuration-repository/techniques/ncf_techniques/technique_by_Rudder/1.0/metadata.xml .... + 33. <VALUE>(ParameterId(command),Write-Host "testing special characters ` è &é 'à é ")</VALUE> - 33. <VALUE>Write-Host "testing special characters ` è &é 'à é "</VALUE> + 34. <VALUE>(ParameterId(command),/bin/echo "testing special characters ` è &é 'à é "\)</VALUE> - 34. <VALUE>/bin/echo "testing special characters ` è &é 'à é "\</VALUE> 35. </REPORTKEYS>
Likely a ._2
is missing on the (paramter, value)
Actions