APPIAN AUTOMATED TESTING

INCORPORATE MODEL-BASED TESTING

Here's how it works:

This functionality definitively addresses regression testing needs.

It enables you to quickly and easily maintain changes in requirements for Appian projects.

It's a significant advancement that aligns with the solution's ethos we've been evolving over the past 10 years, designed to offer you everything:

EASE - SPEED - SAVINGS - EFFICIENCY - QUALITY

By adding this functionality to AAT, we introduce the most powerful and specialized tool, encompassing unique and specific features for automated testing in Appian.

MODEL BASED TESTING:

• Given a test, execute it up to the desired point in real-time. Pause, continue, go back—whatever you require.
• Automatically detect Appian fields on an interface.
• Create tests interactively. Add a behavior, execute it. Change it, execute it again—simply interact!

These features enhance the speed and resilience of the existing powerful functionalities, unmatched by any generic tool in Appian projects.

Appian Automated Testing works with all versions of Appian (v18+), thus ensuring resilience to changes in Appian versions. Generic tools may lose much of the work if Appian introduces changes that affect the layout in its version update.

Let's go through the implications of incorporating Model-Based Testing into three critical aspects when evaluating a testing tool:

• SPEED OF CONSTRUCTION
• RESISTANCE AND EASE OF CORRECTIONS IN THE FACE OF FREQUENT CHANGES
• TEST EXECUTION BEFORE THE LAYOUT IS READY (TRUE BDD)

And if that's not enough...

WE HAVE A SPECIAL OFFER: If you have a test in Selenium and want to switch to AAT, contact us! You won't believe it!

Now, let's delve into some details.

SPEED OF CONSTRUCTION:

One of the standout advantages of Appian Automated Testing, especially with the new Model-Based Testing (MBT) functionality specifically designed for Appian objects and navigations, is its ability to quickly and efficiently build regression tests from scratch.

Thanks to the automatic and precise recognition of Appian objects, teams (even users with no automation experience) can create a complete set of tests tailored specifically to the logic and architecture of their Appian applications. Model-Based Testing applied to object recognition ensures a construction speed unimaginable for any other generic tool in Appian projects.

In no time, you can have the core navigations ready, which represent a significant time investment when testing. You'll save a lot of manual effort, replacing it with machine time.

Quickly obtaining these core navigations with AAT gives you the opportunity to focus on deeper aspects of testing, improving the final quality.

Once you have the core navigation, you can easily add all the verifications corresponding to each object and each piece of data, making tests much more thorough.

As for data, we have everything prepared for you! You can use data creation templates, create data loads, have consistent data among multiple linked tests, repeat navigations with different data, and even clean up data that is no longer useful, keeping your test environment free from failed tests.

You've seen that for data, we have it all. But let us also mention that AAT has a specific functionality to compare data coming from files and services. You can have data from files in PDF, Excel, Mail, or services in XML and JSON. And with any of them, you can compare it with the data entered by the user or even with the values you have within the Appian processes. This functionality is undoubtedly one of the most appreciated as it will greatly facilitate the review of all the files you generate from Appian, the emails you send, or how you are receiving data from services.

You'll eliminate repetitive manual processes in no time and focus more and more on improving quality and accelerating each sprint.

And if you've been automating tests in Appian with Selenium for some time, we know what you've been through:

• Continuous changes in requirements.
• Complexity in navigation and test depth.
• Changes in Appian versions.
• And endless scripting and XPath everywhere!

With AAT, with the Model-Based Testing approach, you have the opportunity to definitively solve these tedious problems.

EFFICIENT MAINTENANCE UNDER CONTINUOUS CHANGES:

The resilience of Appian Automated Testing to changes in Appian version is a crucial advantage in dynamic development environments.

With the addition of personalized MBT, this resilience becomes even more powerful. Teams can maintain accurate and up-to-date tests without wasting time on constant adjustments to automated tests.

Particularly in this scenario, change detection is immediate and complements the excellent previous functionalities for making test modifications.

If we add functional vision to MBT, the result is spectacular: folder organization, functional vision, internal organization of the test into scenarios, its easy parallelism with Jira... Maintenance in the face of changes is not only fast but also contributes to the team's understanding and enriches the documentation environment.

But... not only that. In Appian teams, we have a little problem with staff turnover. AAT has a very flat learning curve. Knowing how to handle the frequent and typical changes in Appian projects is a determining factor, which is why we have paid close attention to functionalities related to this operation, as we are aware that many projects value this point when considering automated testing.

To give you an idea, AAT provides significant time savings, estimated at between 30% and 50% of test maintenance in situations of continuous changes, allowing you to anticipate changes in the test before development (BDD).

AND FINALLY, IN THE CURRENT SPRINT DEVELOPMENT, WE IMPROVE EARLY ERROR DETECTION:

We have mentioned that AAT is probably the only tool capable of having tests ready before development, only starting from the user story and acceptance criteria. AAT allows developers to have their tests prepared while they are doing their development (including the data and test cases they will need). This way, most errors are anticipated at a very early stage of the lifecycle. We offer our support to create a real BDD methodology or review your standards with this approach.

The MBT functionality in practice further accelerates automation itself. You won't fail or have errors in automation 100%. Compare this with the errors you encounter when creating a test script in Selenium or with an RPA!

IN CONCLUSION:

AAT positions itself as the definitive solution for test automation in Appian projects. From building regression to maintenance in the face of continuous changes to testing ongoing sprint development, the tool offers a comprehensive solution that drives innovation and ensures continuous success in the era of digital transformation, such as Appian projects.

For those who have not yet started automating or are considering migrating from tools like Selenium, AAT (Appian Automated Testing) with MBT offers a valuable opportunity.

At CEITA, we operate as a boutique and tailor AAT to your reality.