Manual Software Testing & QA | Live Projects, ISTQB Basic

Types of testing: (1 to 4 types)

There are more than 100 types of testing. In this module, we’re going to summarize the 21 most important types of testing.

The first 4 types of testing are elaborated in this section. These types are explained with relevant examples.

List of Manual Testing Types that we cover in this section:

Types of testing:

1. Black Box Testing

2. White Box Testing

3. Regression Testing

4. Retesting Testing

5. GUI Testing (Graphical User Interface)

6. Browser Compatibility

7. Ad-hoc Testing

8. Backend Testing

9. Recovery Testing

10. Functional Testing

11. Non-functional Testing

12. Security Testing

13. Usability Testing

14. Smoke Testing

15. Alpha Testing

16. Beta Testing

17. Compliance Testing

18. Stress Testing

19. Volume Testing

20. Install Testing

21. Uninstall Testing

Types of testing (5 to 8 types)

Here, we’ll discuss the next 4 types of testing. We’ll explain these particular types of testing with practical examples to provide a better understanding. These examples will help you learn and remember the types of learning.

Types of testing (9 to 12 types):

In this section, we’ll cover the other 4 types of testing. We’ll also cover which testing is specifically done for a particular application. Including real-time examples in this section, will help you understand the type of testing and reduce the complexity of testing to learn.

Types of testing (13 to 16 types):

In this module, we’ll discuss the next four types of testing. Each type of testing is cleared with the examples. It also includes the client requirement, design, and tools required for testing.

Types of testing (17 to 21 types):

In this section, the rest of the testing types are elaborated in depth. Again, each type of testing is explained with practical examples. It also covers the particular test case considered for the type of testing.

Exploratory Testing is a dynamic and hands-on approach to software testing where testers actively explore the application without predefined test cases. The key aspects include:

Simultaneous Learning and Testing: Testers learn about the software while testing it.

Flexibility: Allows testers to deviate from the script to follow potential defects.

Creativity and Intuition: Encourages creative thinking and intuition to discover issues.

Immediate Feedback: Provides rapid feedback on the software’s behavior.

It's beneficial for uncovering unexpected issues and is often used alongside other testing methods to ensure comprehensive coverage.

Risk based testing (RBT) is a strategic approach in software testing that focuses on identifying and prioritizing the most critical areas of a system or application based on potential risks. The core principle of RBT is to allocate testing resources and efforts to those areas of the software that pose the highest risk of failure, which in turn maximizes the effectiveness of the testing process.

In RBT, risks are evaluated based on factors such as the likelihood of occurrence, potential impact on users or business operations, and the probability of detection. The process typically involves the following steps:

1. Risk Identification: This involves recognizing potential risks that could affect the software, including functional failures, performance issues, security vulnerabilities, and usability problems.

2. Risk Assessment: Once risks are identified, they are assessed to determine their potential impact and likelihood of occurrence. This often involves scoring or categorizing risks to prioritize them.

3. Test Planning: Based on the assessed risks, a testing strategy is developed. This strategy focuses on the areas of the software with the highest risk, ensuring that these areas receive more rigorous and comprehensive testing.

4. Test Execution: Tests are executed according to the risk-based strategy. High-risk areas are tested more thoroughly, while lower-risk areas might receive less focus or lighter testing.

5. Risk Mitigation: As testing progresses, findings are used to address and mitigate identified risks. This might involve fixing defects, improving test coverage, or refining the risk assessment as new information emerges.

6. Continuous Review: Risk-based testing is iterative and dynamic. It involves continuous review and adjustment of the testing approach based on new risks that may arise or changes in the software or its environment.

By concentrating on high-risk areas, Risk-Based Testing helps ensure that the most critical aspects of the software are tested thoroughly, improving the overall quality and reliability of the product while optimizing the use of testing resources. This approach is particularly valuable in complex systems where exhaustive testing is impractical or impossible.

Usability Testing is a method used to evaluate how easy and user-friendly a product, website, or application is. It involves observing real users as they interact with the product to identify any issues in the design, navigation, or functionality. The goal of usability testing is to improve the overall user experience by identifying pain points and making necessary improvements, ensuring that the product is intuitive and efficient for users.

Manual Software System, Case Study - Airport Management System

How to write test cases Module 1:

In this section, we’ll discuss how to write the test case for a currency converter. We have covered different labels, the color of the buttons, the text field, and from and to buttons. For writing a test case you need to consider assumptions, test case criteria, test case steps, expected result, actual result, and test case result. The test case result decides whether testing is passed, failed, or deferred.

How to write test cases Module 2:

In this module, we’re going to write a test case for a web page for a School Admission Form. You’ll know the importance of the correct name of control. You'll learn about how to write industry-specific test cases at the end of this section.

How to write test cases Module 3:

We’ll learn how to write a test case for a mobile-based application. The writing test case is similar in this case, just the content varies. You need to be careful when you’re checking the text fields.

How to write test cases Module 4:

In this module, we’ll continue to write test cases. In this case, if the requirements are not met or the design is not ready yet then you’ve to write a test case from a wireframe. In this module, we’ll write a test case for the Taxi booking application. It is also similar to previous cases but here you don’t need to comment on what color, and font are required. Because it’s already mentioned in the requirement document.

How to write test cases Module 5:

In this module, we’ll write a test case for desktop-based applications. We’ll use the same template and the way of writing for the test case will also remain the same. In this module, you’ll also learn about the test script term.

Trello - Project Management Tool:

In this section, we’re going to discuss the importance of test management tools and where they are used. You’ll come to know how to create an account on Trello. After Signup you'll be able to create a structure with a list. There is a list of steps needed to be followed to create a board.

Introduction to Bugzilla:

In this module, we'll learn about software tools that will help us to log the bugs i.e., the Bugzilla tool. Here, we have created a template like a test case. In this case, we’ll give the title to bugs. It also covers the types of bugs that can be encountered.

Working on Bugzilla Tool:

Here, we’ll be looking at how we can use the Bugzilla tool. The understanding of Bugzilla is important in order to use it in a better way. After login in, you’ll be redirected to your dashboard. In this part, we’ll create a new bug and know how Bugzilla works. At the end of this section, you’ll learn about working on Bugzilla Tool.

Introduction to Jira Tool:

In this module, we’ll be looking at the advantages of testing tools we’re using. Here, we’ll explain the features, advantages, and templates of the Jira tool in a detailed manner. You’ll learn testing tools to ease your testing.

Working on the Jira Tool

After covering the features and benefits of the Jira tool in the previous section, we’re going to do hands-on practice with the Jira tool. We’ll include the practical project experience in this section for a clear understanding of Jira tools. You’ll come to know how to create an account on Atlassian using the Jira tool.

Static Reviews Techniques:

In this section, we’re going to discuss the static testing techniques. Basically, we have done two types of testing - Static and Dynamic. In this part, we also differentiate between Static QA and Dynamic QC and where these two techniques are used.

Automation Tools:

In this particular module, we’ll be looking at one of the widely used automation tools. There are different types of automation and manual testing tools. We’ll discuss the different categories of testing tools and their benefits. You’ll go through the 6 major categories.

API Testing through Postman Tool:

The most important topic of the current industry is going to be discussed in this part, API testing. Firstly we’ll understand what API testing is and then understand API testing practically using another tool called Postman and Swagger. API stands for Application Programming Interface.

Mobile Application Testing:

In this module, we’re going to cover the Mobile application testing. It is about testing apps on mobile devices. The mobile could be Android and iOS. In this section, you’ll learn about the difference between web app and mobile app testing.

Introduction QA:

We’ll provide QA in this section asked in the interview.

Interview QA of Manual Software Testing Part 1:

Frequently asked questions in the interview are covered in this section. You’ll be prepared for the interview, and how to attempt the interview. How to appear in any interview conducted for a tester?

Interview QA of Manual Software Testing Part 2:

You’ll get a list of questions asked in a software tester interview. It also includes test levels for testing. You’ll also be taught by an instructor about regression testing and retesting.

Q1. What are the different test levels in software testing?

Q2. Difference between regression testing and retesting?

Q3. When you writing test cases what information you should consider?

Interview QA of Manual Software Testing Part 3:

We’ll continue the series of interview QAs to help you to crack your interview in this section. You’ll know the difference between Black box and White box testing. You’ll learn about the Selenium automation tool for web applications. This section also covers different testing tools.

Q4. What is the difference between black box and white box testing?

Q5. What are the benefits of selenium?

Q6. How many types of tools are there in manual testing?

Q7. Write a test case.

Q8. What are functional and non-functional testing for example?

Q9. What is the tool used for non-functional testing?

Q10. Situation-based questions.