Best way to do unit testing

RE: Best way to do unit testing

kunals0003 — Sun, 22 Sep 2019 04:17:39 GMT

Atleast run all the happy scenarios

Make sure there are no performance issues

Recode any inefficient code (unecessary database calls, unused variables, merge similar code to a single sub-rule)

Test every time you change something and make sure nothing breaks

Spotted a bug? Fix it and run a test to make sure it doesn't happen again

Pass proper arguments to your function and make the test expect the proper return value

Pass a NULL object reference. Do something that generates exceptions

If you have dependencies which are blocking you then modularize the code to remove them and test independently

Unit test according to the acceptance criteria before marking any story as 'Done'

RE: Best way to do unit testing

laurenc20 — Wed, 03 Oct 2018 17:41:50 GMT

While unit testing within the rule can be good at the time, I agree that creating extra test cases and integrating with Jenkins to run the tests daily is a good way to continuously unit test your rules.

docs.appian.com/.../Running_Automated_Tests_on_Expression_Rules_with_Jenkins.html

RE: Best way to do unit testing

ravir0001 — Thu, 20 Sep 2018 16:05:59 GMT

Nitesh, I think you may follow the below similar approach how you test plug-in.

1. A local Appian installation
2. Add <APPIAN_HOME>\\_admin\\_scripts\\classpath.jar to the build path
3. When initializing the unit testing invoke

ConfigurationLoader.initializeConfigurations();

For example

@Before
public void setUp() throws Exception {
ConfigurationLoader.initializeConfigurations();
}

The below links may help on this :

forum.appian.com/.../Expression_Rules.html
forum.appian.com/.../Testing_Process_Models.html
forum.appian.com/.../Interface_Designer.html
community.appian.com/.../checklists

RE: Best way to do unit testing

ajinkyab277 — Thu, 20 Sep 2018 04:43:44 GMT

I prefer checking process history to verify process is working as per expectation or not . And for interfaces I add debug field to verify values are coming as per expectation or not

RE: Best way to do unit testing

Prema Suresh — Wed, 19 Sep 2018 03:00:46 GMT

This was very helpful as I was also in need of some guidelines for Unit testing. Thanks!

RE: Best way to do unit testing

Lokesh Kothari — Mon, 17 Sep 2018 12:03:51 GMT

create test cases using fitnesse tool (automation tool) supported by Appian and are easy to create

RE: Best way to do unit testing

yeswanththiyarir — Fri, 14 Sep 2018 15:57:35 GMT

Hi Nithesh,
It depends on the application you are developing. Best practices suggests to test all the objects at every stage: creationg, using in different object etc.,.
Thanks,
Yeswanth.

RE: Best way to do unit testing

Kevin Gajewski — Thu, 13 Sep 2018 07:37:45 GMT

@Nitesh you can get more guidance about using the expression rule test cases feature for unit testing here as well: docs.appian.com/.../Expression_Rule_Testing.html

RE: Best way to do unit testing

Shanmukha — Wed, 12 Sep 2018 09:56:48 GMT

Hi Nitesh,

You are saying Appian objects which means you want to test each and every object in Appian? We usually perform unit test as soon the object is created with different inputs 1) Positive results 2) Negative 3) No results. We follow same for process model as well. Once we create a process model we will start testing it with providing dummy values for the input parameters and run the flow. For the interfaces as well you can test in the same way with dummy ri inputs.

RE: Best way to do unit testing

Sidhant Behura — Wed, 12 Sep 2018 09:16:01 GMT

Best way to do unit testing is completely subjective. However Appian provides various ways to perform testing.
Please go through them and select the one which best suites your requirement based on your application/project.

docs.appian.com/.../Running_Automated_Tests_on_Expression_Rules_with_Jenkins.html
docs.appian.com/.../Automated_Testing_for_Expression_Rules.html

Also apart from these you can use Appian Fitnesse for testing your application flows.

RE: Best way to do unit testing

ravalik — Wed, 12 Sep 2018 05:51:21 GMT

Hi nitesht,

To unit test your application you can go either of the ways.
Refer the link given below.It might be helpful.
docs.appian.com/.../Running_Automated_Tests_on_Expression_Rules_with_Jenkins.html

Thanks,
ravalik

RE: Best way to do unit testing

Dastagiri Dudekula — Wed, 12 Sep 2018 05:33:01 GMT

List out the appian objects created for the given scenario.
If its independent flow test with required user inputs.
While testing test both positive and negative scenarios.
If its dependent flow test from the flow which will trigger created flow
Check all the requirements mentioned in the acceptance criteria
For Appian objects notice all of its properties like name, description, display names assigned and are appearing in the flow as expected(in case of dynamic name setup)

RE: Best way to do unit testing

sagarl511 — Wed, 12 Sep 2018 04:06:30 GMT

Appian provides smart service/functions to run unit test cases on all expression rules or only on application

Please refer below links -

docs.appian.com/.../Automated_Testing_for_Expression_Rules.html
docs.appian.com/.../Start_Rule_Tests_All_Smart_Service.html
docs.appian.com/.../Start_Rule_Tests_Applications_Smart_Service.html
docs.appian.com/.../Expression_Rule_Testing_Functions.html

Apart from this you can use Fitnesse for unit testing.

RE: Best way to do unit testing

harrisont606 — Tue, 11 Sep 2018 12:52:11 GMT

You can build test cases for all of your expression rules and run them via Jenkins. For workflow testing you can use selenium or fitnesse

docs.appian.com/.../Running_Automated_Tests_on_Expression_Rules_with_Jenkins.html