Requirement for Web App Test Automation Framework
Hi all,
Could I have your expertise on below.
I have a requirement to build a test automation framework for a Web Application. Web application is developed using java and MySQL.
And the domain is related with finance sector.
Most of the functions in the application is working with scheduling services which the service will triggered automatically. Mainly they wanted to verify the data which are displayed in UI with the database. Which means the data which is created with the scheduling services are added correctly.
Some of the testing scenarios are as below:
1. For each transaction it will create a ticket and need verify the data which is on the ticket.
2. There are some configurations ( like rules) which will used to create behaviors of the transactions and have to verify the transactions will work according to the rule.
3. Whether the ticket is created for the correct user.
4. There are notification rules as SMS, Email and Letters, and needed to verify whether the correct notification rule is triggered.
5. Verify if the ticket is automatically closed if outstanding or arrears is fully settled.
For automate this kind of scenarios what is best testing methodology ( tools, BDD vs TDD, framework type) should I use for create the framework and writing the test scripts.
Hope you got the above.
Could you please share your thoughts on this. It will be grateful.
Thank you.
The Common Large Question
Interpretation of the Need and Requirement
- The present execution state of automation
- Looks like no automation is written for this web application
- What's the product?
- It is a finance application
- The web UI is the user interface for this application
- Is there any other user interface for this application?
- Not sure
- What does the product do?
- As said in the requirement,
- The majority of business use case and function flow is to do with scheduling service
- This scheduling happens automatically that is the system takes care of it using the input from the user -- which can be seen as one transaction
- There are rules which can be called configurations
- These rules will define how and what the transaction must do
- Need to validate if the transaction adheres to the set rule
- Need to validate if the ticket is created to the right user using this rule
- Need to validate if the notification rule executed is right
- The different types of notifications available
- SMS
- Letters
- Postal letter?
- Each transaction will create a new ticket
- Validate if the ticket is closed by the system on outstanding credit or arrears is completely settled
- Technology and Tech Stack
- Java and MySQL is used in this web application
- Could be,
- The backend is written in Java
- The database uses MySQL
- But the system as this that involves scheduling and notification will have queuing, caching, messaging, and searching operations
- The tech stack used for this is not mentioned in the requirement
- Imagine a system that has to initiate the postal letter notification
- This is something which involves not just software but also the people interaction very much
- Help Expected from Community
- As written in the question posted
- "For automate this kind of scenarios what is best testing methodology ( tools, BDD vs TDD, framework type) should I use for create the framework and writing the test scripts."
Microservices and Where to Automate
When I have to pick the automation in the large system built using Microservices, I will know what is that I want to accomplish from automation? And, this is one of the primary questions to be answered irrespective of what the system is and how it is built.
Further, this leads me to know and understand:
- What data do I need to test and validate?
- Where to validate data?
- How to validate data?
- Which is faster and more efficient when validating the data?
- What is the expectation when validating the data?
I have missed showing the "data" within the hosting area in the above picture. With that, I ask where should I test and automate to look for what I want to learn. When I have this picture of my system in mind and how the microservices interact with the tech instances, it directs me to talk with appropriate team members and get started.
Getting Started to Automate in this System
Reading the problem statement and what is expected, it is nowhere mentioned by the tester -- how to automate on the web UI or API or other tech instances of the product. But, the tester has mentioned the flows and their outcome which should be covered in the automation.
If I had to start testing and automation, I will do the below and assess:
- APIs:
- I look at how good and deterministic is the APIs in processing the requests
- Can I take the response of API to infer the system looks to function as expected
- If yes, just this has to be taken by the client interface and display the result?
- Can I test the notifications at this layer with help of automation?
- Can I test the rules at this layer with help of automation?
- Can I test for the configuration here?
- Can I test for the ticket creation and its state updates?
- Web UI:
- Do the contract between the web UI and API is obliged or does it have any problem?
- Is there any JS feature on web UI that takes and processes data further?
- If yes, do I need to validate this to understand the correctness degree of the data to decide?
- Or, the web UI just accepts the response and display the data?
- Databases, Queuing, Messaging, and Caching:
- Is there a need that I should be testing and automating at this layer to decide on the data displayed?
- Should I test here in association with other tech instances or in isolation to know the data?
- Is testing of Microservice and its endpoint is sufficient? Or, should I also include these tech instances in testing together with Microservice?
No comments:
Post a Comment
Please, do write your comment on the read information. Thank you.