Showing posts with label software testing. Show all posts
Showing posts with label software testing. Show all posts

What do you need to know to be a Software Test Automation Analyst/Engineer

What you need to know to be a
Software Test Automation Analyst/Engineer
(also called Automation Tester, QA automation)?
 
To Watch in Youtube : click here
   
1.    What do you need to know to be a manual tester ?
 
This was discussed here also.
To watch in YouTube about the manual testing  : click here

You should know what testing is, also called software testing or quality assurance.
What we do in software testing.

1. What is a test case?

Relevant/Helpful links for test case, below: 

 What is a test case, how to write a test case   

2. What is a test plan?
3. What is a requirement(or User Stories)?
4. What is a defect?

Test management tool, better to know 1 or 2 tools
Defect management tool, better to know 1 or 2 tools
Microsoft Word
Microsoft Excel

Knowledge of :
Agile methodology
SQL, Database
API testing



2.    Additional things to know for Testing Automation:
There are different ways, tools, frameworks to automate testing.
In this video we will focus on Testing Automation with JAVA/Selenium.

1.    At least one object oriented programming(OOP) language such as Java or Python or other OOP language(You donot need to be an expert, but the more you know, the better it will be for you in your testing).
2.    Selenium(libraries, dependency)
3.    Automation Frameworks such as Selenium WebDriver, TDD, BDD
4.    An IDE/Editor such as Eclipse or Intellij, Eclipse is more popular

Other things to know:
5.    Git, Github or similar “verson control” tool
6.    Jenkins
7.    DevOPs, CICD

Some popular testing Automation tools : Selenium, Cypress, Pytest(Python), Tricentis Tosca, Appium



What do you need to know to be a manual tester?


To watch in YouTube: click here

Link for : what you need to know to be an Automation Tester, click here , to watch in YouTube, click here

 

You should know what testing is, also called software testing or quality assurance.
What we do in software testing ?

1. What is a test case?

Relevant/Helpful links for test case, below: 

 What is a test case, how to write a test case   


2. What is a test plan?
3. What is a requirement(or User Stories)?
4. What is a defect?

Test management tool, better to know 1 or 2 tools
Defect management tool, better to know 1 or 2 tools
Microsoft Word
Microsoft Excel

Good to have knowledge of below topics, many of the projects require these nowadays:
What is agile methodology? => more common nowadays
SQL, Database  => more common nowadays
API testing


Test Plan

To watch in YOUTUBE, click here

Test Plan(Test Planning) in Software Testing

Test Plan is a detailed document about the testing process to be carried out. It includes the detailed information about testing objectives, estimation , activities, resources and schedule etc.


A Test Plan includes below information:

1. Objectives
2. Approach
3. Resources
4. Software
5. Hardware
6. Environments
7. Test Schedule
8. Deliverables
9. Responsibilities
10. Features to be tested
11. Features not to be tested
12. Entry and Exit criteria
13. Risks and contingencies
14. Pass Fail criteria
15. Estimation of time / cost
16. Assumptions and Dependencies
17. Approval Criteria

Objectives:
This talks about the objectives , the goal of the testing.

Approach:
It defines the testing steps, methods, types, testing process or techniques.

Resources:
This talks about the resources required in terms of technical skills, number of resources , team structure, size etc.

Software:
This talks about the software or application , database , web services, network configurations , operating systems etc required for testing.

Hardware:
This talks about the required hardware , machines , Virtual machines etc.

Environments:
This talks about the number of testing environments required for the testing. We might require more than one testing environments based on functionalities, properties, dependencies.

Test Schedule:
This talks about the test schedule,  how much time we need, when we will start and complete the testing.

Deliverables:
These are test documents or reports or other testing artifacts which testing team gives to the stakeholders. The artifacts are given before the testing , during the testing and after the testing.

Responsibilities:
It defines the roles and responsibilities of the team members.

Features to be Tested:
It is the scope of testing. It defines the list of the features  of the software or the  product,  which are in scope. The features mentioned in this section will be tested.

Features not to be Tested;
This also talks about the scope of the testing. It defines the list of features of the software or product which are out of scope of the testing. They will not be tested.

Entry and Exit Criteria:
Entry Criteria defines the conditions or requirements to be fulfilled before starting the testing. Such as availability of all software , access to the testers , test data, test environment being up and running etc.
Exit Criteria defines the conditions or requirements to be fulfilled before declaring the test as complete. Such as deadlines, coverage of requirements and functionalities , no defects left at the end etc.

Risks and contingencies:
Every project is associated with some risks, you should be ready for possible risks and should have proper mitigation plan for them. The risks are assumed based on previous experience, information and result. The common risks are: lack of resources, lack of software or hardware , lack of skill , late delivery of the code, change in the requirement, risk of budge/cost or time etc.
When the risk takes place, then you should come up with the appropriate solution. Some common actions for the risks are : shifting the delivery date(this is not recommended though) , changing(usually reducing the functionalities for testing ) the scope of testing, adding resources etc. For the kind of risk, if appears, whichever step is most appropriate , that step will be taken.

Pass Fail criteria:
It is a minimum standard or criteria for completing the test. To mark the test as PASSED, the criteria should be fulfilled. Such as , the product should be defect free or sometimes it will be acceptable with minor defects. This does not talk about individual test result, it talks about the testing of the overall product or software under test.

Estimation of time / cost:
Time : It talks about the time required to complete the testing , in other word, the deadline to complete testing.
Cost : It is the budget for the testing.

Assumptions and Dependencies:
It is part of risk management. The risks are future unexpected events which might occur. So, you make proper assumptions based on your experience, information and result.
The testing activities might be dependent on so many factors such as data, environment, resources, proper coordination especially when the team members are not working from the same place. You have to prioritize and carryout  the testing activities accordingly.

Approval Criteria:
You will need approval of the test plan and other deliverables at different stages of testing(before testing, during testing, after completing the testing). The client or stakeholders can approve the test plan or the deliverables. You take the approver's name , role, signature and approval date.

QA interview questions and answers part 1

To watch in YouTube: click here

1.      What is black box testing and white box testing ?

Black Box Testing: It is testing of the application or product in which we do not test the back end, internal structure or the code.

White Box Testing: It is a testing of the application or product in which we test the back end, internal structure or the code.

 

2.      What is Software Testing Lifecycle (STLC) ?

The software testing lifecycle is the steps from the beginning to the end of the testing. It involves below steps:


3.      What is a test case ?

A test case is a testing artifact that has the testing steps, testing data, preconditions, status(pass/fail), actual result, expected result etc. The test case shows whether the functionality being tested satisfied the software requirement or not.

 

4.      What is a test plan?

A test plan is a document that has a detailed picture of the testing activities to be included in the testing. It has the objectives, schedule, scope, dependencies, entry/exit criteria, pass/fail criteria, resources, and other information related to the testing to be carried out to deliver a quality product.

 

5.      What is non-functional testing ?

The testing which does not include testing of functionality is non-functional testing. Such as performance testing, load testing, security testing, usability testing etc. Similarly, the testing of documents, requirements, environment, network, user access, etc also fall under non-functional testing.

 

6.      What is load testing ?

It is a testing to find out the product or software’s threshold point or limitation. In this, the load is increased to test how much load a software or product can handle or manage before it breaks. In a practical situation, a number of virtual users are created and access the application concurrently by the users. This test determines whether the application remains stable or not under actual load conditions.

 

7.      What is stress testing ?

It is a testing to find out how the application or software behaves when the load is increased up to the breaking point, or the load crosses the threshold.  This testing is done to check the application response in abnormal conditions.  We check if the system reaches the breaking point, does it show the right error message, does it recover after it fails.

 

8.      What is regression testing ?

A regression testing is a testing of a product or software after a new fix or change has been added to the product.  After a fix or change has been added, then we have to test the new functionality which was fixed or changed, or newly added. Regression testing comes into the picture after we do the testing of the new functionality. We test the overall product to test if the remaining functionality is working fine or not, if the new functionality has impacted other existing functionality or not. To check if there are any new bugs because of the change.

 

9.       What is verification and validation ?

Verification: It determines if the software or product meets the business requirement or specifications.

Validation: It determines if the software or product meets the client’s expectations.

 

10.     What is the difference between Verification and Validation ? 

To watch in YouTube, click this link: Verification and Validation in Software Testing

1. Verification is the process of determining if the product meets the business requirements or specifications.
2. We test the design, codes, data, front end, back end.
3. Done while the product is under development.
4. Involves low level testing such as reviews, inspections, analysis.
5. Finds bugs early
6. Verification is done before Validation
7. Tested by software testers, QAs

1. Validation is the process of determining if the product meets client’s expectation or need.
2. We validate the actual product.
3. Done after the product is developed.
4. Involves high level testing such as Performance/Load/Stress Testing,  black box testing, white box testing, grey box testing
5. Finds bugs missed by verification.
6. Validation is done after Verification.
7. Tested by client/customer/UAT.

 

What is the difference between the priority and severity ?

To watch in YouTube, click : What is the difference between the priority and severity ?

Priority:

1. Priority indicates how important is the issue to be fixed. It indicates the order of the defect to be fixed.

2. Priority is figured out based on the business requirement or process.

3.The priority might change over time.

4. Priority could be mainly High, Medium, Low

Severity:

1. Severity indicates what is the impact of the issue.

2. The severity is figured out based on the impact on the functionality and performance and the impact on the end-user experience.

3. It normally does not change over time.

4. Severity could be mainly Critical, Major, Moderate, Minor

 


QA Questions and Answers Part 1

 Software Testing Interview Questions and Answers, part 1

1.      What is black box testing and white box testing ?

Black Box Testing: It is testing of the application or product in which we do not test the back end, internal structure or the code.

White Box Testing: It is a testing of the application or product in which we test the back end, internal structure or the code.

 

2.      What is Software Testing Lifecycle ?

The software testing lifecycle is the steps from the beginning to the end of the testing. It involves below steps:

Gathering Requirements and Analysis

Creating Test Plans

Create Test cases

Set up, and configure test environment

Test execution

Close the test cycle

 

3.      What is a test case ?

A test case is a testing artifact that has the testing steps, testing data, preconditions, status(pass/fail), actual result, expected result etc. The test case shows whether the functionality being tested satisfied the software requirement or not.

 

4.      What is a test plan?

A test plan is a document that has a detail picture of the testing activities to be included in the testing. It has the objectives, schedule, scope, dependencies, entry/exit criteria, pass/fail criteria, resources, and other information related to the testing to be carried out to deliver a quality product.

 

5.      What is non-functional testing ?

The testing which does not include testing of functionality is non-functional testing. Such as performance testing, load testing, security testing, usability testing etc. Similarly, the testing of documents, requirements, environment, network, user access, etc also fall under non-functional testing.

 

6.      What is load testing ?

It is a testing to find out the product or software’s threshold point or limitation. In this, the load is increased to test how much load a software or product can handle or manage before it breaks. In a practical situation, a number of virtual users are created and access the application concurrently by the users. This test determines whether the application remains stable or not under actual load conditions.

 

7.      What is stress testing ?

It is a testing to find out how the application or software behaves when the load is increased up to the breaking point, or the load crosses the threshold.  This testing is done to check the application response in abnormal conditions.  We check if the system reaches the breaking point, does it show the right error message, does it recover after it fails.

 

8.      What is regression testing ?

A regression testing is a testing of a product or software after a new fix or change has been added to the product.  After a fix or change has been added, then we have to test the new functionality which was fixed or changed, or newly added. Regression testing comes into the picture after we do the testing of the new functionality. We test the overall product to test if the remaining functionality is working fine or not, if the new functionality has impacted other existing functionality or not. To check if there are any new bugs because of the change.

 

9.   What is verification and validation ?

Verification: It determines if the software or product meets the business requirement or specifications.

Validation: It determines if the software or product meets the client’s expectations.

 

10. What is the difference between Verification and Validation ?

Verification is the process of determining if the product meets the business requirements or specifications.
We test the design, codes, data, front end, back end.
Done while the product is under development.
Involves low level testing such as reviews, inspections, analysis.
Finds bugs early
Verification is done before Validation
Tested by software testers, QAs

Validation is the process of determining if the product meets client’s expectation or need.
We validate the actual product.
Done after the product is developed.
Involves high level testing such as Performance/Load/Stress Testing,  black box testing, white box testing, grey box testing
Finds bugs missed by verification.
Validation is done after Verification.
Tested by client/customer/UAT.