Make it easy to run all tests (cppunit and marionette)
Reported by Christopher Stawarz | April 20th, 2010 @ 06:55 PM
Right now, there's a single test runner for all cppunit-based tests, but there's no canned way to run all marionette tests and summarize the results. It'd be nice to have a single test runner that ran both the cppunit and marionette tests and provided a single results report.
The easiest thing would be to write a wrapper script (shell or Python) that runs all the tests and aggregates and summarizes the results. A more elegant approach would be to integrate the marionette tests into the cppunit machinery and use the existing cppunit test runner.
Comments and changes to this ticket
-
Christopher Stawarz May 6th, 2010 @ 05:50 PM
- State changed from “new” to “open”
- Assigned user set to “Christopher Stawarz”
The
test_mworksscript (added in commit 80070007dab93e01f581ff5332be136f1c34e6c7) implements the easy approach. However, we should still consider implementing the elegant approach at some point. -
Christopher Stawarz July 9th, 2010 @ 01:01 PM
- Milestone order changed from “0” to “0”
It looks like you can add cppunit tests at runtime by creating TestCase instances.
-
Christopher Stawarz October 17th, 2012 @ 11:08 AM
- State changed from “open” to “resolved”
The easy approach has been working fine for a while now, so I'm calling this resolved
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The core framework and supporting libraries for the MWorks Suite
Christopher Stawarz