What is a Test Plan?

Lets Plan our Testing

A Test Plan is a document which defines the systematic approach of execution of testing and step by step approach of activities of testing. The Test Plan contains a detailed understanding of the eventual workflow of testing.

Definition of Test Plan:

According to Testing Maturity Model Integration (TMMI)

“The purpose of Test Planning is to define a test approach based on the identified risks and the defined test strategy, and to establish and maintain well-founded plans for performing and managing the testing activities”.

The plans are to be prepared by Test/QA Leads or by Project Managers only. In all test plans, the ETVX {Entry-Task-Validation-Exit} criteria are to be mentioned. Entry means the entry point to that phase. For example, for unit testing, the coding must be complete and then only one can start unit testing. Task is the activity that is performed.

Validation is the way in which the progress and correctness and compliance are verified for that phase. Exit tells the completion criteria of that phase, after the validation is done. For example, the exit criterion for unit testing is all unit test cases must pass.

ETVX is a modeling technique for developing worldly and atomic level models. It stands for Entry, Task, Verification and Exit. It is a task-based model where the details of each task are explicitly defined in a specification table against each phase i.e. Entry, Exit, Task, Feedback In, Feedback Out, and measures. 

So know more about Software Testing Read

Testing Made Easy V2.0

Testing Made Easy V2.0 :

Buy it online : 

 https://www.amazon.in/Testing-Made-Easy-v2-0-Evolution-ebook/dp/B00MAOD5DS

Scope of Testing

What is Scope of Testing?

A Scope of Testing is where we define what to test and what not to 

test.It clearly defines our area of testing the application or system.

Unless we are clear with our scope or area of testing it is not advisable to start our testing.The testing team describes specifically what you want to accomplish by identifying what you will test and what you will not.

For example, you might limit your testing of client computer hardware to the minimum supported configurations or to the standard configurations.

To know more on Software Testing:

Read : Testing Made Easy V2.0 available in Amazon

https://www.amazon.in/Testing-Made-Easy-v2-0-Evolution-ebook/dp/B00MAOD5DS

Cost of Quality

What is COQ “The Cost of Quality”?

“Every time work is redone, the cost of quality increases”

The "cost of quality" is not the price of creating a quality product or service. It’s the cost of NOT creating a quality product or service.It does not include costs associated with maintenance and quality training.

Examples include:

•The reworking of a manufactured item.

•The retesting of an assembly.

•The rebuilding of a tool.

•The correction of a bank statement.

•The reworking of a service, such as the reprocessing of a loan operation or thereplacement of a food order in a restaurant.

In short, any cost that would not have been expended if quality were perfect contributes to the cost of quality.

The Total Quality Costs are the total of the cost incurred by:

•Investing in the prevention of nonconformance to requirements.

•Appraising a product or service for conformance to requirements.

•Failing to meet requirements.

To know more about Software Testing :

Buy Testing Made Easy V2.0 :

https://www.amazon.in/Testing-Made-Easy-v2-0-Evolution-ebook/dp/B00MAOD5DS

Attitude of a Software Tester

 ATTITUDE OF A SOFTWARE TESTER

 Attitude matters a lot for everything & particularly for S/w Tester. It reflects the way he sees the application.A tester is always a bridge between the client & company.

He should possess the below qualities:

Ø  Passion for analysis & testing.

Ø  Logical & Technical Capability.

Ø  Flexibility.

Ø  Communication Skills

Ø  Business Sense.

Ø  Constructively Destructive Sense

To know more about Software Testing. 

Please Buy : 

https://www.amazon.in/Testing-Made-Easy-v2-0-Evolution-ebook/dp/B00MAOD5DS 

A Comparison of Testing with Quality Assurance and Quality Control

                       

A Comparison on Testing with QA & QC

Quality Assurance: It is an activity where we ensure that we implement the process, procedures & Standards. We implement all these through various methods to accomplish our goals and include ensuring conformance to one or more standards, such as ISO 9000 or a model such as CMMI. It is process oriented & preventive activity and a subset of STLC.

Quality Control: It is an activity which ensures that the requirements are verified for software. The implementation of procedures and process are followed with full focus on Actual Testing. It is product oriented activity and a corrective process. It is considered as the subset of QA.

Testing: It is an activity which ensures that we identify the 

fallacies of the software where the focus is on actual testing. It is 

Product Oriented activity with a preventive process. It is a subset of Quality Control.

To know more on Software Testing
Buy my book at : https://www.amazon.in/Testing-Made-Easy-v2-0-Evolution-ebook/dp/B00MAOD5DS

History of Software Testing

History of Testing 

Software Testing came into existence in 1960, not in a structured manner but it was the beginning. The oblivious reason of the birth or rather the need for a testing came because of lack of established standards of software engineering practices. Poor design and Regular hardware up gradation left many types of software in-effective and thus a strong need arose in the industry to produce faster and highly reliable software. The requirement of Software Testing increased with the increasing dependency on software along with good engineers.

Software Testing Originated to address the below issues:

• Enhance the  processes,
• Increase the reliability of product,
• Deliver a quality product,
• Deliver in time

D. Gelperin and W.C. Hetzel in their Book The Growth of Testing has briefly defined the classification in the below.They classified for software testing the following phases and goals:

• Until 1956 it was the debugging oriented period, where testing was often associated to debugging and there was no clear difference between testing and debugging.
• From 1957-1978 there was the demonstration oriented period where debugging and testing was distinguished now - in this period it was shown, that software satisfies the requirements.
• The time between 1979-1982 is announced as the destruction oriented period, where the goal was to find errors.
• 1983-1987 is classified as the evaluation oriented period: intention here is that during the software life cycle a product evaluation is provided and measuring quality.
• From 1988 on it was seen as prevention oriented period where tests were to demonstrate that software satisfies its specification, to detect faults and to prevent faults

Start, Accelerate & Zoom

Let's Automate - A Brief on Automation Testing 

     

      Automation Testing means using an automation tool to execute your test case suite. Automation testing is also known as Test Automation is when the tester writes scripts and uses an Automation Tool to test the software. This process involves automation of a manual process. Automation Testing is used for test scenarios for which we need to re-run the test scenarios for multiple times.

 Whatis.com defines it as " Automated testing tools are capable of executing tests, reporting outcomes and comparing results with earlier test runs. Tests carried out with these tools can be run repeatedly, at any time of day. The method or process being used to implement automation is called a test automation framework."

    The Objective of Automation Testing is 

• simplifying testing efforts
• usage of Manual intervention to the minimal

The automation software can also enter test data into the System Under Test, compare expected and actual results and generate detailed test reports.

Test Automation stresses a need of considerable investments of money and resources.Successive development cycles will require execution of same test suite repeatedly. Using a test automation tool it's achievable to record this test suite and re-play it as required. Once the test suite is automated completely, we do not require any human intervention is required. This improved ROI(Return of Investment) of Test Automation.

The Automation tools are very useful to speed up the test cycle as they can replicate manual testing processes at a much faster rate.Goal of Automation is to reduce number of test cases to be run manually and not eliminate manual testing all together. The Main Criteria or the Success Mantra automated software testing is by and large most successful when implemented by expert resource.

Automated testing is important due to following reasons:

• Testing of all the Workflows, Functionalities and Negative Scenarios is time consuming & also cost.
• Automation Testing is best suited for testing which requires testing the volume of data.
• It is difficult to test for multi lingual sites manually.
• It’s very useful for testing the performance of websites or an application.
• Automation increases speed of test execution.
• Automation helps increase Test Coverage.
• Manual Testing is error prone as it’s a repeated activity involving human intervention.

What can we automate?

Automation is best suited for the following criterion to increase the automation ROI

•        Critical Business Requirements which are of High Risk.
•     Repeated Execution of Test Cases
•         Test Cases that is very monotonous or difficult to perform manually.
•     Test Cases which are lengthy.

       To Conclude on this above topic i would say automation is the way forward to make life better for testers but not to forget that unless you are strong in your basics of what to test and what not to any testing method will be of no use.... So lets learn our basics to move forward...