If in single suite will exist empty or duplicated URLs (this might happen fairly easy on huge suites) you will get ambiguous messages while running "malformed" xml.
The message presented on jenkins on older version of aet (2.1.3):
[ERROR] Failed to process test suite: 'Not Found'
The message presented on jenkins on lastest version of aet (3.1.0):
[ERROR] Failed to schedule test suite: '[Status: 400] Bad Request
Please provide ERROR message which will be more informative OR prevent it in some other way.
Please run below code and unncomenty one of urls to see a failure.
<?xml version="1.0" encoding="UTF-8"?>
<suite name="testing" company="cognifide" project="cog" domain="https://www.cognifide.com">
<test name="Accessibility" useProxy="rest">
<collect>
<resolution width="1920"/>
<open/>
<accessibility standard="WCAG2AAA" />
</collect>
<compare>
<accessibility report-level="ERROR" />
</compare>
<urls>
<url href="/contact-us"/>
<!--<url href=""/>-->
<!--<url href="/contact-us"/>-->
</urls>
</test>
</suite>
Cheers!
If in single suite will exist empty or duplicated URLs (this might happen fairly easy on huge suites) you will get ambiguous messages while running "malformed" xml.
The message presented on jenkins on older version of aet (2.1.3):
[ERROR] Failed to process test suite: 'Not Found'The message presented on jenkins on lastest version of aet (3.1.0):
[ERROR] Failed to schedule test suite: '[Status: 400] Bad RequestPlease provide ERROR message which will be more informative OR prevent it in some other way.
Please run below code and unncomenty one of urls to see a failure.
Cheers!