about 1 month ago
There are three weeks remaining in the AppianWORLD20 Hackathon! Submissions are due February 7, 2020 before 5pm ET. (Find out what time this is in your city)
Bonus Tech Tip: Testing your application
Testing is an on-going activity and instills confidence that your application will work as you expect it to. Before you start writing tests, you should decide what kind of testing your application needs and how much time you need to invest in it.
There are three types of testing you can do with Appian:
- Unit Testing
Unit testing focuses on the smallest testable parts of your application. The goal is to validate that your logic or rules behave as expected under various conditions. For example, you should test display and validation logic as you’re developing an interface, rather than waiting until the end of your development cycle to test it.
- User Interface (UI) Testing
Testing from a user’s perspective validates the end-to-end experience and your design choices. You should do it early and often as you’re developing to make sure your application meets the user’s needs. For example, if you have a related action that updates record data, UI testing ensures that the correct users can access the form and that the information is updated successfully.
- Performance Testing
Performance testing ensures that your application will scale and behave as expected during production-like or peak usage. When making changes you should take into consideration the size of your data and the frequency of each action. For example, how well will your application perform if you have a record grid with many rows of data and you have “x” number of users who need to interact with the data on that grid.
Check out the full Appian Documentation on Testing Applications here.
If you have any questions about the hackathon, please post on the discussion forum.