How and why do we tag the complexity and severity to a defect?

Normally, the complexity of a defect

The severity of a defect, in the context of testing, refers to the effect the defect has on the software product/system. So for each defect, we need to identify like how critical the defect is, and how much effect it is going to have on our product. A defect that completely hampers or blocks testing of the product can be considered as a critical defect. When a defect has only minor or no effect on the final result of the product, we can consider it as a low defect.

Defect Priority and Severity levels

(Pic source:

A4 to go

• What is Automation Testing?
• What are the benefits of Automation Testing?
• Why should Selenium be selected as a test tool?
• What is Selenium? What are the different Selenium components?
• What are the testing types that can be supported by Selenium?
• What are the limitations of Selenium?
• What is an Xpath?
• What are locators? Name commonly used locators?
• When, why and how do you automate a test case?
• What are the different types of locators in Selenium?
• What is difference between assert and verify commands?
• What is an Xpath?
• What is the difference between “/” and “//” in Xpath?
• What do we mean by Selenium 1 and Selenium 2?
• How do I launch the browser using WebDriver?
• What are the different types of waits available in WebDriver?
• How to type in a textbox using Selenium?
• How can you find if an element in displayed on the screen?
• How can we get a text of a web element?
• How to select value in a dropdown?
• What are the different types of navigation commands?
• How to handle frame in WebDriver?
• When do we use findElement() and findElements()?
• How to find more than one web element in the list?
• What is the difference between driver.close() and driver.quit command?
• Can Selenium handle windows based pop up?
• How to assert title of the web page?
• How to mouse hover on a web element using WebDriver?

Agile Testing

Agile testing is a software testing practice which follows agile software development principle. It involves all members of a cross-functional agile team, with special expertise contributed by different testers. Agile testing is an iterative testing method, and it requires collaborations between the customer and self-organising team and aligns development with customer needs.

So how agile testing is working?

Project Team

(Pic from

So, here, for each iteration, an integrated working product increment has resulted, and the result is delivered for User Acceptance Testing (UAT).



Continuous integration is the key of Agile. Unlike traditional Waterflow model, Agile requires a depth of continuous collaboration between stakeholders of a project, including managers, developers, testers, and customers.

Why do organisations prefer Agile methodology over Waterfall or any other methodologies?

Comparing with traditional testing methodologies, Agile Testing saves time and money, and requires less documentation. The regular meetings of Agile Testing can also help determine the issues or upcoming problems well in advance. Also, the company, or the team of the software system can receive regular feedbacks from the end users.

In contrast, traditional waterfall model treats analysis, design, coding, and testing as discrete phases in a software project. When we are in the second stage, it is impossible for us to go back to the previous stage. (1) It can cause poor quality when the project runs out of time and money, and testing is the only phase left to do. Under this situation, the testing phase will be cut off. (2) Also poor visibility. We will never know where we are when we are doing a waterfall project. (3) Also, it is quite risky. Too late to go back.


A2 and A3

Assignment 3

15. \
16. \
18. How do you plan your test case execution?
19. What does severity and priority mean while logging a defect
20. How do you provide test case effort estimation?
21. What is Risk Based Testing?
22. What is defect triaging?
23. Difference between QA and QC?
24. How to overcome the challenge of not having input documentation for testing?
25. Explain Test Strategy?