I just implemented this on my local system and it seems to work well. I use it for HTTPUnit tests and not JUnit tests. There are a couple of improvements that I'd like to see and wondering if they are in the pipline or not.
1. I need my JUnit tests to have access to the servlet. I don't want to push my tests to production so I will make checkboxes in the UI with environment variables and test Prod using our internal DEV box.
2. I'd like to be able to point my test sources outside of the jar. Example: (notice /local/lib/Test.jar)
<init-param>
<param-name>searchResources</param-name>
<param-value>/local/lib/Test.jar</param-value>
</init-param>
Are these enhancements in the works?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just implemented this on my local system and it seems to work well. I use it for HTTPUnit tests and not JUnit tests. There are a couple of improvements that I'd like to see and wondering if they are in the pipline or not.
1. I need my JUnit tests to have access to the servlet. I don't want to push my tests to production so I will make checkboxes in the UI with environment variables and test Prod using our internal DEV box.
2. I'd like to be able to point my test sources outside of the jar. Example: (notice /local/lib/Test.jar)
<init-param>
<param-name>searchResources</param-name>
<param-value>/local/lib/Test.jar</param-value>
</init-param>
Are these enhancements in the works?
Thanks.