The role of QA (Quality Assurance) is to monitor the quality of the “process” used to produce the software. While the software testing, is the process of ensuring the functionality of final product meets the user’s requirement.

 

Testware is test artifacts like test cases, test data, test plans needed to design and execute a test.

 

Build: It is a number given to Installable software that is given to the testing team by the development team.

Release: It is a number given to Installable software that is handed over to the customer by the tester or developer.

 

  • Mastering the automation tool
  • Reusability of Automation script
  • Adaptability of test case for automation
  • Automating complex test cases.

 

Bug release is when software or an application is handed over to the testing team knowing that the defect is present in a release. During this the priority and severity of bug is low, as bug can be removed before the final handover.

Bug leakage is something, when the bug is discovered by the end users or customer, and not detected by the testing team while testing the software.

 

Data driven testing is an automation testing framework, which tests the different input values on the AUT. These values are read directly from the data files. The data files may include csv files, excel files, data pools and many more.

 

  • Once the bug is identified by the tester, it is assigned to the development manager in open status
  • If the bug is a valid defect the development team will fix it.
  • If it is not a valid defect, the defect will be ignored and marked as rejected
  • The next step will be to check whether it is in scope. If the bug is not the part of the current release then the defects are postponed
  • If the defect or bug is raised earlier then the tester will assign a DUPLICATE status
  • When bug is assigned to developer to fix, it will be given a IN-PROGRESS status
  • Once the defect is repaired, the status will change to FIXED at the end the tester will give CLOSED status if it passes the final test.

 

 

The test strategy includes an introduction, resource, scope and schedule for test activities, test tools, test priorities, test planning and the types of test that has to be performed.

 

  • Unit testing
  • Integration testing and regression testing
  • Shakeout testing
  • Smoke testing
  • Functional testing
  • Performance testing
  • White box and Black box testing
  • Alpha and Beta testing
  • Load testing and stress testing
  • System testing

 

The testing of all the branches of the code, which is tested once, is known as branch testing. While the testing, which is focused on the limit conditions of the software is known as boundary testing.

 

  • Testing objectives
  • Testing scope
  • Testing the frame
  • The environment
  • Reason for testing
  • The criteria for entrance and exit
  • Deliverables
  • Risk factors

 

Agile testing is software testing, is testing using Agile Methodology. The importance of this testing is that, unlike normal testing process, this testing does not wait for the development team to complete the coding first and then doing testing. The coding and testing both goes simultaneously. It requires continuous customer interaction.

 

Test case is a specific condition to check against the Application Under Test. It has information of test steps, prerequisites, test environment, and outputs.

 

  • The strategy for Automation Test Plan
  • Preparation of Automation Test Plan
  • Recording the scenario
  • Error handler incorporation
  • Script enhancement by inserting check points and looping constructs
  • Debugging the script and fixing the issues
  • Rerunning the script
  • Reporting the result

 

The systematic and independent examination for determining the effectiveness of quality control procedures is known as the quality audit.

 

QA testing document should include

  • List the number of defects detected as per severity level
  • Explain each requirement or business function in detail
  • Inspection reports
  • Configurations
  • Test plans and test cases
  • Bug reports
  • User manuals
  • Prepare separate reports for managers and users

 

MR stands for Modification Request also referred as Defect report. It is written for reporting errors/problems/suggestions in the software.

 

Software QA document should include

  • Specifications
  • Designs
  • Business rules
  • Configurations
  • Code changes
  • Test plans
  • Test cases
  • Bug reports
  • User manuals, etc

 

 

Validation activities should be conducted by following techniques

  • Hire third party independent verification and validation
  • Assign internal staff members that are not involved in validation and verification activities
  • Independent evaluation

 

 

The testing of all the branches of the code, which is tested once, is known as branch testing. While the testing, that is focused on the limit conditions of the software is known as boundary testing.

Cross Browser Testing is a type of non-functional test which helps us ensure that our website or web application works as expected in various web browsers. We could do Cross Browser Testing on different browsers both manual and automated way.
To do Cross Browser Testing manually, we (Software Testers) create tests for each browser and execute it manually on each browser. To do it in an automated way, we could create Selenium tests with multiple conditional statements that execute test cases based on a specified browser type.
Every browser displays a website in their own style. We usually cannot have all the browsers on one machine. Each browser is designed by a different vendor.
So each browser has its own features to showcase its unique presence. While testing a website, we need to ensure that our website is appearing the same across all the browsers.
To do this we need to have all the browsers. Fortunately, there are some tools to perform cross-browser testing without testing individually in a manual way.
Compatibility testing: Testing an application on different hardware or software platform is Compatibility testing. Example: Different devices such as iPhone, Samsung, etc., Different operating systems such as Windows, Linux, etc.,
Cross-browser testing: Testing a web application on different browsers is Cross-browser testing. Cross-browser testing is a subset of Compatibility testing.
Example: Google Chrome, IE 10, IE 11, Firefox 43, etc.,

The role of QA (Quality Assurance) is to monitor the quality of the “process” used to produce the software. While software testing is the process of ensuring the functionality of the final product meets the user’s requirement.

Test ware is test artifacts like test cases, test data, test plans needed to design and execute a test.

Build: It is a number given to Installable software that is given to the testing team by the development team. Release: It is a number given to Installable software that is handed over to the customer by the tester or developer.

  • Mastering the automation tool
  • Reusability of Automation script
  • The adaptability of the test case for automation
  • Automating complex test cases.
Bug release is when the software or an application is handed over to the testing team knowing that the defect is present in a release. During this, the priority and severity of bug are low, as the bug can be removed before the final handover.
Bug leakage is something when the bug is discovered by the end-users or customer, and not detected by the testing team while testing the software.

Data-driven testing is an automation testing framework, which tests the different input values on the AUT. These values are read directly from the data files. The data files may include CSV files, excel files, data pools and many more.

A cookie is also known as an HTTP cookie, web cookie, internet cookie, browser cookie.
CRUD (Create, Read, Update and Delete) is another term used for Black box testing. CRUD testing is another term for database testing.
C – Create – Creating a new Transaction
R – Read/Retrieve – Searching or viewing a transaction
U – Update – Editing or modifying an existing transaction.
D – Delete – Deleting a transaction from the database of software testing.
  • Once the bug is identified by the tester, it is assigned to the development manager in open status
  • If the bug is a valid defect the development team will fix it.
  • If it is not a valid defect, the defect will be ignored and marked as rejected
  • The next step will be to check whether it is in scope. If the bug is not the part of the current release then the defects are postponed
  • If the defect or bug is raised earlier then the tester will assign a DUPLICATE status
  • When the bug is assigned to the developer to fix, it will be given an IN-PROGRESS status
  • Once the defect is repaired, the status will change to FIXED at the end the tester will give CLOSED status if it passes the final test.

The test strategy includes an introduction, resource, scope and schedule for test activities, test tools, test priorities, test planning and the types of test that has to be performed.

  • Unit testing
  • Integration testing and regression testing
  • Shakeout testing
  • Smoke testing
  • Functional testing
  • Performance testing
  • White box and Black box testing
  • Alpha and Beta testing
  • Load testing and stress testing
  • System testing
A software quality assurance engineer has to perform the following tasks:
– Understanding of software design
– Knowledge of source code
– Code review
– Version control
– Program testing
– Integration testing
– Release process
  • Software QA document should include
  • Specifications
  • Designs
  • Business rules
  • Configurations
  • Code changes
  • Test plans
  • Test cases
  • Bug reports
  • User manuals, etc
  • Selenium
  • Firebug
  • OpenSTA
  • WinSCP
  • YSlow for FireBug
  • Web Developer toolbar for firebox

Above are just sample tools. The tools a Tester may vary with his/her project.

  • Load Testing: Testing an application under heavy but expected load is known as Load Testing. Here, the load refers to the large volume of users, messages, requests, data, etc.
  • Stress Testing: When the load placed on the system is raised or accelerated beyond the normal range then it is known as Stress Testing.
  • Volume Testing: The process of checking the system, whether the system can handle the required amounts of data, user requests, etc. is known as Volume Testing.

 

  • Setting up the requirements criteria, the requirements of a software should be complete, clear and agreed by all
  • The next thing is the realistic schedule like time for planning , designing, testing, fixing bugs and re-testing
  • Adequate testing, start the testing immediately after one or more modules development.
  • Use rapid prototype during design phase so that it can be easy for customers to find what to expect
  • Use of group communication tools

 

The document that describes, the user action and system response, for a particular functionality is known as USE case. It includes revision history, table of contents, flow of events, cover page, special requirements, pre-conditions and post-conditions.

 

CRUD stands for Create, Read, Update and Delete. CRUD testing can be done using SQL statements.

 

A thread testing is a top-down testing, where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

 

It is a process to control and document any changes made during the life of a project. Release control, Change control and Revision control are the important aspects of configuration management.

 

It is a testing phase where the tester tries to break the system by randomly trying the system’s functionality. It can include negative testing as well.

 

A software quality assurance engineer tasks may include following things amongst others

  • Writing source code
  • Software design
  • Control of source code
  • Reviewing code
  • Change management
  • Configuration management
  • Integration of software
  • Program testing
  • Release management process

 

  • The stub is called from the software component to be tested. It is used in top down approach
  • The driver calls a component to be tested. It is used in bottom up approach
  • It is required when we need to test the interface between modules X and Y and we have developed only module X. So we cannot just test module X but if there is any dummy module we can use that dummy module to test module X

 

A bug triage is a process to

  • Ensure bug report completeness
  • Assign and analyze the bug
  • Assigning bug to proper bug owner
  • Adjust bug severity properly
  • Set appropriate bug priority

 

To support testing during development of application following tools can be used

  • Test Management Tools: JIRA, Quality Center etc.
  • Defect Management Tools: Test Director, Bugzilla
  • Project Management Tools: Sharepoint
  • Automation Tools: RFT, QTP, and WinRunner

 

A cause effect graph is a graphical representation of inputs and the associated outputs effects that can be used to design test cases.

 

In software testing, Test Metric is referred to the standard of test measurement. They are the statistics narrating the structure or content of a testing. It contains information like

  • Total test
  • Test run
  • Test passed
  • Test failed
  • Tests deferred
  • Test passed the first time

 

A test matrix is used to map test scripts to requirements.

 

Retesting is carried out to check the defects fixes, while regression testing is performed to check whether the defect fix have any impact on other functionality.

 

Software quality practices includes

  • Review the requirements before starting the development phase
  • Code Review
  • Write comprehensive test cases
  • Session based testing
  • Risk based testing
  • Prioritize bug based on usage
  • Form a dedicated security and performance testing team
  • Run a regression cycle
  • Perform sanity tests on production
  • Simulate customer accounts on production
  • Include software QA Test Reports

 

The rule of a Test Driven Development is to prepare test cases before writing the actual code. Which means you are actually be writing code for the tests before you write code for the application.

 

The types of documents in SQA are

  • Requirement Document
  • Test Metrics
  • Test cases and Test plan
  • Task distribution flow chart
  • Transaction Mix
  • User profiles
  • Test log
  • User profiles
  • Test incident report
  • Test summary report

 

MR: MR stands for Modification Request. It is used to change the existing functionality in software, it is usually requested by clients.
ER: ER stands for Enhancement report. It is used to add a new feature in the software. It is usually requested by clients.
  • Testing scope
  • Testing the frame
  • The environment
  • Reason for testing
  • The criteria for entrance and exit
  • Deliverables
  • Risk factors

Agile testing is software testing, is testing using Agile Methodology. The importance of this testing is that, unlike the normal testing process, this testing does not wait for the development team to complete the coding first and then doing testing. Coding and testing go simultaneously. It requires continuous customer interaction.

The test case is a specific condition to check against the Application Under Test. It has information of test steps, prerequisites, test environment, and outputs.

  • The strategy for Automation Test Plan
  • Preparation of Automation Test Plan
  • Recording the scenario
  • Error handler incorporation
  • Script enhancement by inserting checkpoints and looping constructs
  • Debugging the script and fixing the issues
  • Rerunning the script
  • Reporting the result
The systematic and independent examination for determining the effectiveness of quality control procedures is known as the quality audit.
  • Selenium
  • Firebug
  • OpenSTA
  • WinSCP
  • YSlow for FireBug
  • Web Developer toolbar for the firebox
  • Above are just sample tools. The tools a Tester may vary with his/her project.
Setting up the requirements criteria, the requirements of software should be complete, clear and agreed by all The next thing is the realistic schedule like time for planning, designing, testing, fixing bugs and re-testing Adequate testing, start the testing immediately after one or more modules development.
Use rapid prototype during the design phase so that it can be easy for customers to find what to expect Use of group communication tools
Load Testing: Testing an application under heavy but expected load is known as Load Testing. Here, the load refers to the large volume of users, messages, requests, data, etc.  Stress Testing: When the load placed on the system is raised or accelerated beyond the normal range then it is known as Stress Testing.
Volume Testing: The process of checking the system, whether the system can handle the required amounts of data, user requests, etc. is known as Volume Testing.

The document that describes, the user action and system response, for a particular functionality, is known as the USE case. It includes revision history, table of contents, the flow of events, cover page, special requirements, pre-conditions, and post-conditions.

CRUD stands for Create, Read, Update and Delete. CRUD testing can be done using SQL statements.

A thread testing is top-down testing, where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

It is a testing phase where the tester tries to break the system by randomly trying the system’s functionality. It can include negative testing as well.

  • A software quality assurance engineer tasks may include following things amongst others
  • Writing source code
  • Software design
  • Control of source code
  • Reviewing code
  • Change management
  • Configuration management
  • Integration of software
  • Program testing
  • Release management process
  • The stub is called from the software component to be tested. It is used in a top-down approach
  • The driver calls a component to be tested. It is used in the bottom-up approach
  • It is required when we need to test the interface between modules X and Y and we have developed only module X. So we cannot just test module X but if there is any dummy module we can use that dummy module to test module X

Bug triage is a process to Ensure bug report completeness Assign and analyze the bug Assigning the bug to proper bug owner Adjust bug severity properly Set appropriate bug priority

To support testing during development of application following tools can be used
  • Test Management Tools: JIRA, Quality Center, etc.
  • Defect Management Tools: Test Director, Bugzilla
  • Project Management Tools: Sharepoint
  • Automation Tools: RFT, QTP, and WinRunner

Start the change

Register to become an Instructor

Please login to fill in this form.

  • Your name
  • Your email
  • Your phone number
  • Your message

I’m a Copywriter in a Digital Agency, I was searching for courses that’ll help me broaden my skill set. Before signing up for Rob’s.