Follow

Testing Your Zapp

Prior to pushing your Zapp to Production, it is imperative that you first complete testing. Testing your Zapp will enable you to find misconfigurations and edge cases that would later cause errors as well as improvements that can be made to the user experience.  This article covers our recommended best practices for testing.


Testing Your Zapp within the Capriza Designer

 

Before distributing your Zapp to a test group of users, you should first perform initial testing via Test mode in the Capriza Designer. To access test mode, click the Test icon in the toolbar.

 

Test.png

 

Test mode allows you to verify the functionality of your Zapp as it will behave in the hands of users on their devices on the right-hand side, while showing the actions taken on the Zapp in the virtual browser on the left-hand side.

 

 

Screen_Shot_2017-07-19_at_2.26.50_PM.png

 

You may restart the Zapp at the login page or first page (depending on settings) via the Start Over icon in the upper right hand corner.

Various settings are also available in the Test Settings dialog to enable you to better evaluate the login and caching settings of your Zapp and the associated end user experience. Please refer to Test Settings for further details.

 

Start_Over.png

 

Run through all possible workflows in your Zapp multiple times with different user logins and types and different combinations of settings enabled. 

Things to look for while testing include:

  • Does the Zapp perform the desired business process in the packaged application?
  • Have you captured all the screens possible in the desired business process?
  • Are warnings or error messages captured?
  • Does the Zapp work properly for different types of users with different permissions?
  • Do you encounter any errors when navigating through the Zapp?
  • How is the end user experience upon subsequent authentications with saved credentials and cookies cached?
  • If you've configured caching for your first page, have you chosen appropriate controls to configure as interactive?

 

Zapp Test Group

 

After completion of testing within the Designer, you should publish your Zapp and distribute it to a subset of users. Not only will this enable you to catch issues with user permissions or experience not seen in the Designer, but it is also a great opportunity to obtain feedback directly from the people who will be using you Zapp.

 

In general, the users you choose should enable you to: 

  1. Test your Zapp with Different User Roles/Accounts 

Make sure that your test group includes multiple types of users who have different access permissions to the system you are zapping (admins, regular users, etc.) to ensure that the different roles are accounted for and that the Zapp works well across all user types.

 

Different user types may have different views of the same application. For example, admins may be able to view more fields or columns or permitted to take more actions than a regular user. If you grab a control that only some types of users are able to see or use, make sure the control is optional so as not to cause unexpected errors in the zapp.

 

Testing your zapp with different user types will help identify these differences and make sure all users have a great experience.

  1. Test Across Devices

Zapps execute with a modern user experience on any platform or form factor that runs a modern browser. Zapps also adapt to any form factor, including smartphones, tablets, and desktops, providing a consistent and rich user experience.

 

Ensure the users within the test group reflect the variety of device types and OSs that are used throughout your organization. By testing across multiple devices, you can make sure the Zapp UI works well across different screen sizes and, for example, is not stretched or squeezed.



 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.