[MAGNOLIA-260] (patch) add support for httpunit tests Created: 06/Jan/05 Updated: 23/Jan/13 Resolved: 23/Jan/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | build |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | 2.01 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Description |
|
while trying to refactor some magnolia custom tags or gui control, I've set up a basic infrastructure to run httpunit tests in magnolia. I am attaching a zip containing new files and the modified project.xml and project.properties. What do you get? You can see a HttpUnitTestCase class which is the base class to use for creating new tests and a sample testcase, composed of 2 files: You can run the sample test using maven on in your favorite ide. Just run "maven eclipse" or "Maven idea" to update your classpath with httpunit dependecies and run ButtonTest as a junit test. You should see the output from the html page and then the test failing with an assertion (yes, the html generated by those buttons is ugly) Now you can easily see the output from you custom tags and having automated tests. PS. this stuff is the same that drives tests in the displaytag project http://displaytag.sourceforge.net |
| Comments |
| Comment by Fabrizio Giustina [ 06/Jan/05 ] |
|
new and modified files, sorry :/ |
| Comment by Fabrizio Giustina [ 23/Jan/05 ] |
|
committed to svn. Test run by maven still fails for classloader issues, work fine in outside maven |