UAT and non-regression testing

Dear all,

I have an application that assesses children symptoms, classify the
illness, and provide guidance for treatment. Many combinations can result
from the implemented logic.
Hence, I need to run non-regression tests and user acceptance tests to make
sure that nothing or only the intended changes were made between two
application versions.
Ideally, I would be able to send a batch of test cases to CommCare with all
the required input in the form, and CommCare would fill in the outputs. In
other words, I’d like to test all the possible form’s combinations.

Is there any way of doing this kind of testing other than manually through
the device?

Thank you,

Alex

Alex,

This something we’re looking into; however, we don’t have any built-in
tools in our platform for doing this at the moment.

Internally we have some tools for doing this using Android and Java testing
frameworks; however, using these requires programming knowledge and a
functional development environment
https://github.com/dimagi/commcare-odk/wiki/Building-CommCareODK-with-Android-Studio-and-Gradle.
If you’re interested in learning more about these options, please contact
me directly at wpride@dimagi.com

Best,
Will

··· On Wed, Aug 26, 2015 at 11:16 AM, Alexandre Vanobberghen < alexandre.vanobberghen@gmail.com> wrote:

Dear all,

I have an application that assesses children symptoms, classify the
illness, and provide guidance for treatment. Many combinations can result
from the implemented logic.
Hence, I need to run non-regression tests and user acceptance tests to
make sure that nothing or only the intended changes were made between two
application versions.
Ideally, I would be able to send a batch of test cases to CommCare with
all the required input in the form, and CommCare would fill in the outputs.
In other words, I’d like to test all the possible form’s combinations.

Is there any way of doing this kind of testing other than manually through
the device?

Thank you,

Alex


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi,

I’d like to +1 Alexadre’s point. It would be great to have some way of
automatically testing form logic based on pre-defined inputs.

Cheers,

··· On Wednesday, August 26, 2015 at 6:05:13 PM UTC+2, William Pride wrote: > > Alex, > > This something we're looking into; however, we don't have any built-in > tools in our platform for doing this at the moment. > > Internally we have some tools for doing this using Android and Java > testing frameworks; however, using these requires programming knowledge and > a functional development environment > . > If you're interested in learning more about these options, please contact > me directly at wpr...@dimagi.com > > Best, > Will > > On Wed, Aug 26, 2015 at 11:16 AM, Alexandre Vanobberghen < alexandre.v...@gmail.com > wrote: > >> Dear all, >> >> I have an application that assesses children symptoms, classify the >> illness, and provide guidance for treatment. Many combinations can result >> from the implemented logic. >> Hence, I need to run non-regression tests and user acceptance tests to >> make sure that nothing or only the intended changes were made between two >> application versions. >> Ideally, I would be able to send a batch of test cases to CommCare with >> all the required input in the form, and CommCare would fill in the outputs. >> In other words, I'd like to test all the possible form's combinations. >> >> Is there any way of doing this kind of testing other than manually >> through the device? >> >> Thank you, >> >> Alex >> >> -- >> You received this message because you are subscribed to the Google Groups >> "commcare-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to commcare-user...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > >