In every earlier test-case we created the Markua input file manually and then we created the expected DOM in JSON representation also manually.
When we implemented the parsing and testing of Markua resources we ran the tests first and then took the dump of the error message and used that to create the JSON representation of both the DOM and the error report. It was a bit of unnecessary manual work. After all we could convert the generated DOM to JSON. Look at it to verify that we really want that to be the expected results and then save it as the expected JSON.
How can we make this easier?
Perl Maven Pro - screencasts with articles
As a Perl Maven Pro subscriber you will enjoy a growing library of articles and screencasts.
Two screencasts a week and all the previous screencasts!
Ad free browsing!
The articles contain topics such as Web Application Development, Object Oriented programming, testing, deployment, code walkthroughs, best practices, and many more subjects in Perl, and in related technologies.
The related technologies over HTML5, CSS3, JavaScript, Git, Subversion, vim, Unix/Linux shell, SQL and NoSQL just to name a few topic that I, as a Perl programmer find useful.
Subscriptions include all previous pro episodes.
In order to subscribe to the Perl Maven Pro, first register and login to the web site, and then pay via PayPal:
or
If you already have Perl Maven Pro subscription, you will need to login to access the articles.
Gabor who runs the Perl Maven site helps companies set up test automation, CI/CD
Continuous Integration and Continuous Deployment and other DevOps related
systems.