I would handle this by a slightly different method, given that you are creating a mock web server.
Since the data you're retrieving depends so heavily on the time, I would use a mock/fake time service that returns predetermined times rather than the system time. That way you will be able to work with a deterministic known set of data rather than having to ...
There is no one standard industry "norm" people have to adhere to.
Coincidentally, I recently had a XML validation experience myself.
As a tester, I was working in an Agile team for 8 weeks. The project we were working on required cooperation from two external development teams, both of which located in a different city.
A XML file was what we used to ...
using your favorite script language would probably be the best solution, Peter suggested Perl and I'll add Python to the list, both have excellent modules to parse and analyze CSVs and XMLs and a lot of capabilities to help you in your tasks.
Looks like you are missing TagSoup in your classpath. As it is stated here you should have one to be able to successfully import html format. Since html is often not a well-formed XML, it should be pre-processed before importing.
When one does not have TagSoup the input format is considered as XML and has to be well-formed. Your example is missing closing &...
I've done this in a variety of ways, so there is not a definitive approach. You need to find the approach that best meets your needs.
Approach One - In the test step that calls the service, e.g. getLocations, I've wrote a Groovy script assertion that compare the number of locations in the response with the number of locations in the db. E.g. select count(*...
I prefer to ask for forgiveness than to ask for permission and many companies and managers share this principle although not always admit that openly.
If there's something innovative to be tried where it is hard to convince people upfront to support something I've learned it's better to try it myself or within a small group. If it worked for you it will be ...
XML Schema Assertion uses javax.xml.parsers.DocumentBuilder.parse() method which stops parsing XML file after the first error.
You can work it around by implementing your own ErrorHandler in i.e. Beanshell Assertion
Add Beanshell Assertion instead of the XML Schema Assertion
Put the following code into the Beanshell Assertion "Script" area:
Instead of testing with csv / xml level. You can load the data into a database and run queries and obtain accurate results
Create a Results DB with Run_Id (ex-ResultMMDDYYY_1)
Load the source and destination data into the DB
Run Queries for each source / destination tables and create a results table
Fetch the data from results table and publish results