It would be very helpful and timesaving if a test option for actions and webservices would be integrated in Service Studio. Instead of creating test screens, setup test data and publish espace to create your own test set.

This test action should include:

possibility to set input parameters

debug mode

Merged from 'Actions and Webservices test functionality' (idea created on 2012-04-26 09:15:53 by Rene Sundermeijer), on 2014-01-24 12:51:46 by Gonçalo Borrêga

Joop Stringer

5 May 2012

I like this ... now I use soapUI to test webservices ... but the way soapUI handles webservices is different then how OutSystems handles them

Merged from 'Actions and Webservices test functionality' (idea created on 2012-04-26 09:15:53 by Rene Sundermeijer), on 2014-01-24 12:51:46 by Gonçalo Borrêga

It could be samething as a scrapbook, I would like very much if it was possible to test a build in function in this way. Till now what I do is to create a page with what I want to test, publish and test the function, a lot of wasted time is lost.

The reason why I don't think this has been done before is that, unlike Test Query, the platform needs to generate the code (either C# or Java) in order to allow proper execution. As such, while testing a query is somewhat easier, testing a piece of code is not.

</PersonalOpinion>

With this in mind, I decided to take this path on my Masters Degree Project/Thesis. What I intend to do is a Testing Framework component that "automatically" gets your User Actions and generates the unit test cases to achieve branch coverage. There are other features intended but this is the major one.

Why couldn't those be test parameters as we have in test query? We already have that pattern implemented, so surely that can't be the reason...I tend to agree with Armando Gomes with the on the fly generation of code and execution. But heck, it does not need to be instant we surely can handle the wait for a few seconds to get that up and running

Nobody said it was easy :) And I really like this discussions since we can always learn something new.

What I'm trying to build is something that could help you save some time when doing the tests. It would generate them for you and it would also execute those, given a few possible limitations that I'm not really sure right now.

So, yeah. In the end it could be something like a "test action" but not-so-instant.

Again, any suggestion, feel free to use the link above or firing me a message. I'm more than eager to get views and inputs from other people.