Designing Contexts and Actions for modal windows in ACCELQ

What are Contexts and Actions in ACCELQ?

A context in your application is a placeholder that denotes a particular state of the application (for UI testing) or something that serves as a container for functionality relevant to that state (for API, DB testing, etc.). If you are working with Web UI testing, a context can be a webpage(for web apps), a screen(for mobiles), or any window that performs some functions. 

The context contains actions. An action is defined as a significant test function. An action can be to log in to the web application, insert or update some information, log out, etc. 

Designing Contexts and Actions for modal windows

Modal windows provide the functionality for designing context and actions to support modularity. This helps in breaking down the more significant problems into smaller parts. It makes testing easier. 

The following two examples will help you understand the concept of designing contexts and actions for modal windows. 

Example 1

For instance, consider a modal window with the following characteristics. 

• The modal window can be initiated from multiple places in the application. 
• It performs a standalone functionality.
• After the actions are performed, the application reaches a fixed page. The initiation place does not change the outcome page.
   

One example of such a modal is the New Lead modal in the salesforce application. As you can see in below picture, the New Lead can be initiated from three different places. It can be initiated from the Leads > New Lead option. It can be initiated by the + symbol at the top right corner. It can also be initiated by the New button. 

Credit: accelq.com.

After you have created the Lead, the application always reaches the Lead Information Page. This page is navigated regardless of the initiation place. 

You can have the following design attributes for contexts and actions for such a modal. 

• Create the modal as a separate view in a context from where it can be accessed(from any three places). Or it can also be created as a separate context in itself. 
• Separate the actions and steps in the modal itself. For example, create an action to “Initiate New Lead” and “Create New Lead.” The “Initiate New Lead” will invoke the modal. The “Create New Lead” will accomplish the actual functionality. 
  • Share the “Initiate New Lead” action with all the context from where it can be invoked. 
  • “Invoke New Lead” action will be present individually in each originating context. 
• For the “Create New Lead” action, set the “Lead Information Page as the destination page. 

Example 2

Let us take another example. Consider another modal window with the following attributes.

• This modal is a part of the main flow of primary action. 
• Adds other features/functionalities. 
• It can be applied to multiple pages. 
• This modal reaches the initiation page after actions are performed. It does not land on a fixed page like the above example. 
   

You can take the example of the “entity search” modal in the salesforce application. This modal does not perform a standalone functionality. It can be invoked from multiple places. It adds the functionality of performing the search operation. When the modal finishes, the application navigates to the same page from where it was initiated. 

Credit: accelq.com.

You can have the following design attributes for contexts and actions for such a modal.

• It can be considered as a separate view in an existing context. Do not consider this modal as a separate context. 
• Separate the actions in invoking(“Invoke Search Modal”) the modal and performing the functions of the modal. The actions can be to search and select items.
  • Share the Search action with all relevant contexts.
  • The “Invoke Search Modal” will be defined by each originating context separately. 
• Set the destination of the Search action to “Current Context.” The destination is not a fixed page but the initiating page. 

Frequently Asked Questions❔

What is ACCELQ?

ACCELQ is the complete Test Automation and Management Platform. It works with natural English coding and self-healing capabilities. It is used as codeless test automation software based on AI and analytics. 

Is it easy to use ACCELQ? If yes, why?

Yes, it is easy to use ACCELQ to automate and manage testing for your applications. It uses plain English and a Codeless testing approach. It uses AI to understand natural language, which makes things easier. 

Do you need a framework to use ACCELQ?

ACCELQ performs automation with no framework overhead. It is a fully cloud-based DevOps and Agile Ready platform. You can create an account on ACCELQ and start using the test automation provided by ACCELQ.

How does ACCELQ work?

ACCELQ works on the design-first approach, which means you can visualize your scenarios or test data in your universe within ACCELQ.

What are the contexts in ACCELQ?

A context in your application is a placeholder that denotes a particular state of the application (for UI testing) or something that serves as a container for functionality relevant to that state (for API, DB testing, etc.).

Conclusion🔚

This article discussed designing Contexts and Actions for modal windows in ACCELQ. To learn more about Automation Testing Tools, visit Automation Testing Tools - Coding Ninjas Coding Ninjas Studio. 

Learn more concepts of ACCELQ by following the below links.

🔗 What is ACCELQ? 

🔗 What are the data type and data lists in ACCELQ? 

🔗 Parameterization in ACCELQ.

🔗 Context and its Creation in ACCELQ.

🔗 Running manual tests in ACCELQ. 

🔗 Over Parameterization adds to maintenance effort in ACCELQ. 

🔗 Project Admin - Status List in ACCELQ. 

I hope you would have gained a better understanding of these topics now!

Are you planning to ace the interviews with reputed product-based companies like Amazon, Google, Microsoft, and more? 

Attempt our Online Mock Test Series on Coding Ninjas Studio now!

Happy Coding!