I would like to hear from people how they have approached automated testing of servoy applications, as well as unit testing. All input welcome!
Here are some topics to consider sharing:
-What 3rd party test tools have you used and how well did they work?
-How have you approached unit testing?
-Have you created any modules within servoy that are meant to help with your automated testing?
-What languages have you used to write testing against servoy apps?
-How does testing web client differ from the smart client in your use of tools?
-How do you manage sets of test data, moving them in and out of the database to setup for specific tests? (I’m using mysql)
We have a good testing background, but on other platforms, so we’re looking to get our bearings in servoy.
Thanks for any insight!
This is a topic of interest to me as well. I’ve tossed around ideas for a while, and decided to wait for v4 to get serious about testing my solutions.
v4 is, of course, now here, so it’s definitely time to open this discussion. There is a session on Testing at ServoyWorld, which I look forward to very much.
It would be great if the community could come together around some “best practices” for Servoy solution testing.
g.
I’ll throw out a bit about what we’re doing in the non-automated test arena here too.
We use Rally (http://www.rallydev.com) for all of our project management. We are an Agile-oriented shop and this web-based tool is dead-on for agile methodologies.
In it, you can create user stories, then tasks, defects, and test cases against the user stories. You prioritize the backlog of user stories and defects into iterations & releases. As we do each iteration, we have a thorough suite of test cases for every piece of functionality. The tests make sure to address the user stories so we know we’re testing what the client has described. Right now, all of our testing is manual
OUr plan is to build a smoke test suite, so every time we touch code, we run the smoke tests and make sure all prior functionality still works as new things are added or defects are fixed.
We’re evaluating a product out of Germany called Squish (Marcel–go check them out for us! ![:)]( "Smile")
. It seems very robust for automated testing, but it’s a little pricey for a small shop. If it fits the bill, we are leaning that way, but still want other input.
And we haven’t even begun to get into load testing Servoy…but we will.
Please share your ideas. We need more community around testing. Good testing makes good software and good software brings more clients!