EDUCBA

EDUCBA

MENUMENU
  • Free Tutorials
  • Free Courses
  • Certification Courses
  • 600+ Courses All in One Bundle
  • Login
Home Software Development Software Development Tutorials Software Testing Tutorial Software Testing Principles
Secondary Sidebar
Software Testing Tutorial
  • Basics
    • What is Software Testing
    • Careers in Software Testing
    • Defect Life Cycle in Software Testing
    • Bug Life Cycle
    • Levels of Software Testing
    • Software Testing Life Cycle
    • Software Tester Work
    • Software Testing Principles
    • Software Testing Services
    • Testing Methodologies
    • Test Approaches
    • Grey Box Testing
    • Types of Software Testing
    • What is a Bug in Software Testing
    • Benefits of Automation Testing
    • What is Automation Testing?
    • Types of Automation
    • Typical Journey of a Software Tester
    • Automation Testing Process
    • Mobile Automation Testing
    • Automation Testing Life Cycle
    • Software Quality Assurance
    • Software Quality Assurance
    • What is Test Environment?
    • Verification and Validation Testing
  • Types of Testing
    • Adhoc Testing
    • Types of System Testing
    • Manual Testing Types
    • Unit Testing Types
    • Unit Testing Benefits
    • Agile Testing
    • What is Agile Testing
    • Acceptance Testing
    • Stress Testing Types
    • Alpha and Beta Testing
    • Application Testing
    • Automation Testing
    • Automation Testing Advantages
    • Benchmark Testing
    • Black Box Testing
    • Domain Testing
    • Dynamic Testing
    • Ecommerce Testing
    • Fuzz Testing
    • Gray Box Testing
    • GUI Testing
    • Installation Testing
    • Interface Testing
    • Interoperability Testing
    • Mainframe Testing
    • Manual Testing
    • Mutation Testing
    • Monkey Testing
    • Negative Testing
    • Penetration Testing
    • Penetration testing phases
    • Penetration testing framework
    • Protocol Testing
    • Recovery Testing
    • Regression Testing
    • Mobile Penetration Testing
    • Accessibility Testing
    • Sanity Testing
    • Scalability Testing
    • Security Testing
    • Spike Testing
    • Stability Testing
    • State Transition Testing
    • Static Testing
    • Gatling Load Testing
    • System Integration Testing
    • Structural Testing
    • Locust Load Testing
    • System Testing
    • Control Flow Testing
    • Unit Testing
    • Cypress testing
    • Volume Testing
    • Web Testing Application
    • What is Exploratory Testing
    • What is Stress Testing
    • What is Usability Testing
    • White Box Testing
    • Types of White Box Testing
    • Compatibility Testing?
    • Use Case Testing
    • Beta Testing
    • Integration Testing
    • Non Functional Testing
    • Non Functional Testing Types
    • What is Functional Testing
    • Functional testing types
    • Cookie Testing
    • Alpha Testing
    • Boundary Value Testing
    • Equivalence Class Testing
    • Glass Box Testing
    • SOA Testing
    • Smoke Testing
    • Visual Testing
    • Visual Paradigm
    • Model-Based Testing
  • Testing techniques
    • Software Testing Methodologies
    • Black Box Testing Techniques
    • Static Testing Techniques
    • Test Case Design Techniques
    • What is Static Analysis
  • Testing tools
    • Manual Testing Tools
    • Visual Testing Tools
    • Automation Testing Tools
    • Functional Testing Tools
    • GUI Testing Tools
    • Penetration Testing Tools
    • Performance Testing Tools
    • SOA Testing Tools
    • Accessibility Testing Tools
    • What is QTP
    • Regression Testing Tools
    • Security Testing Tools
    • Test Management Tools
    • Defect Management Tools
    • Code Coverage Tools
    • Test Coverage Tools
    • Defect Tracking Tools
    • Continuous Integration Tools
    • Install Bugzilla
    • Test data generation tool
    • Unit Testing Tools
    • Web Testing Tools
    • Stress Testing Tools
    • Performance Monitoring Tools
    • Mobile Testing Tools
    • Responsive Testing Tool
    • Cross Browser Testing Tools
    • Risk Based Testing
    • Database Testing Tools
    • WinRunner
    • What is Squish?
    • CubicTest
    • What is WinRM?
    • Bugzilla Tool
    • Code review tools
    • Penetration Testing Open Source Tools
  • Advance
    • Cyclomatic Complexity
    • Decision Table Testing
    • Decision Tree Algorithm
    • What is Continuous Integration
    • Mantis Bug Tracker
    • Equivalence Partitioning
    • Gantt Chart Software
    • Acceptance Testing Types
    • Load testing tools
    • Install TestNG
    • Install Unity
    • Defect Management Process
    • Test Plan Template
    • Testing Interview Questions
    • Testing of Mobile application
    • What is Test Automation Frameworks
    • Test Automation Framework
    • Application of Automation
    • Test Automation Process
    • Automation Testing Roles and Responsibilities
    • What is Instruction Cycle?
    • What is Cucumber?
    • 15 Best Popular Bug Reporting Tools
    • What is Automated Testing?
    • Software Maintenance Types
    • Types of Penetration Testing
    • Software Reliability
    • Best Gantt Chart Software
    • Code Coverage
    • Branch Coverage
    • Decision Coverage
    • Statement Coverage
    • What is Test Case
    • Types of Test Case
    • What is Test Scenario
    • Formal Review
    • Alpha Beta Pruning
    • What is Cyclomatic Complexity?
    • Test Coverage
    • How to Write Test Case
    • Testing Documentation
    • Performance Testing Life Cycle
    • Test Harness
    • Test Strategy
    • Software Incident Management
    • What is Debugging
    • What is Defect?
    • Listeners in TestNG
  • Inteview Questions
    • Automation Testing Interview Questions
    • Manual Testing Interview Questions
    • ISTQB Interview Questions
    • Cucumber Interview Questions
    • Software Testing Interview Questions
    • Penetration Testing Interview Questions

Related Courses

Software Testing Course

Penetration Training Course

TestNG Training Course

Software Testing Principles

By Mahantesh NagathanMahantesh Nagathan

software testing principles

Introduction to Software Testing Principles

Software Testing Principle is a process of testing the result or output of a product with an expected output of a client. In other words, we can say that the evaluation of systems or components to find the specified requirements. It executes identifying the gaps, errors, defects in the product, quality of software being developed, completeness, or missing requirements to match specified requirements.

Before moving to software testing principles, we will see some concepts of software testing briefly as discussed below:

Software Testing History

The testing of the product began in the year 1979 by Glenford J. Myers, who introduced the process of debugging the products.  His main intention was to work on breakage testing, a simple test case to detect undiscovered errors and separate fundamental development activities, such as debugging, errors, etc., from the software engineering community.

Who does Testing?

In big industries or companies, there will be a team of associated stakeholders of the project to conduct the testing based on the process. They will analyze the software on the given requirements.

Start Your Free Software Development Course

Web development, programming languages, Software testing & others

Following are the professionals who involved in a testing process depending on their respective capacities:-

All in One Software Development Bundle(600+ Courses, 50+ projects)
Python TutorialC SharpJavaJavaScript
C Plus PlusSoftware TestingSQLKali Linux
Price
View Courses
600+ Online Courses | 50+ projects | 3000+ Hours | Verifiable Certificates | Lifetime Access
4.6 (86,697 ratings)
  • Software Tester
  • Software Developer
  • Project Manager
  • End-User

There are different types of roles that test the software or product based on their experience and knowledge, such as Software Tester, Software Quality, Assurance Engineer, QA Analyst, etc.

Principles of Software Testing

Software testing is an extremely challenging task. The principles of software define instructions for development teams to find the errors or effects of a project. Following are the seven fundamental principles of software testing:-

Principle 1: Testing shows the Presence of Defects

Testing is a process that shows the presence of defects in the application. It shows the defects but cannot prove that there are no defects. Meaning that the testing team cannot say that the product is 100% defect-free. It reduces the number of undiscovered defects in the application. You cannot assume that the tested application is 100% error-free, even though testing is done. Therefore, design the needed test cases to find the defects as much as possible.

Principle 2: Exhaustive Testing is Impossible

There is less possibility of testing with combinations of inputs, data, test scenarios, and preconditions as they will take more time to test the process. Therefore, the testing team can use some important testing criteria effects such as risk and priorities instead of doing exhaustive testing.

For instance, consider there are 15 fields in one screen, which contains 5 possible values. To test all combinations, you would need 30 517 578 125 (515) tests. But, project timescales would never allow testing a large number of combinations. Because of this reason, test effects called risk and priorities are used to test important features.  So, accessing and managing risk is considered as the most important and essential activities for testing in any project.

Principle 3: Early Testing

In this stage, testing activities will be conducted in the software or system development life cycle to find the defects as soon as possible and to focus on defined objectives. Testers can start testing the products if they have the availability of product requirements or documents.

The main advantage of early testing is testers can easily detect errors, bugs and help in each level of development with fewer costs and efforts.

If errors are found in an initial stage of the development life cycle, then it will be easier and cheaper to fix, and also, the cost of quality will be less. Otherwise, if they found late, then you need to change the whole system process. The testing team will have a deep understanding of the product as they were involved from the beginning of the requirement gathering and analysis phase.

Principle 4: Defect Clustering

This phase includes defects related to a small number of modules, which are tracked during pre-release testing. It means that small modules will have more defects in the system. In the Pareto Principle application, software testing is approximately 80:20, which means 80% of the problems are found due to 20% of the modules.

Defect clustering uses the knowledge and experience of the testing team to recognize the potential modules to test. That forecast can help save time and effort as the team only needs to focus on those “sensitive” areas. There is a small drawback of this phase when testers focus on a small area of the team; they may fail to miss the bugs from other areas.

Principle 5: Pesticide Paradox

This phase is used to review test cases systematically and uses different types of tests to find more defects of the software or system. If you are running the same tests again and again, then there is less chance of getting new bugs that are discovered by these test cases.

You cannot apply these tests to the whole system but can be applied to some limited modules. Testing teams will often review and update the test cases in order to cover different types of sections of the projects.

Principle 6: Testing is Context Dependent

Testing is basically content dependent; projects and products include different elements, features, and requirements. In this approach, different types of sites can be tested differently, and the same test cases cannot be applied for different projects.

For example, safety and critical software will be tested differently than an e-commerce site, or an application in the banking industry will be tested more than entertainment software. There are different types of methodologies, techniques, and types of testing based on the nature of an application.

Principle 7: Absence of Errors Fallacy

If there is an absence of errors in the application, or if the system built is unusable and does not meet the user’s expectations, then finding and fixing defects will not help. If there are no bugs in the software, then you should not consider that software is ready to be used; because testing should be conducted along with the right requirements.

Conclusion

So far, you have seen that seven principles of software testing provide reliable product quality by testing the products. These principles can be applied for testing the project and coding. The main objective of this life cycle process is to find correctness, completeness, quality and detecting errors in the software.

Recommended Articles

This has been a guide to Software Testing Principles. Here we discuss the basic concepts, history and top 7 Principles of software testing, respectively. You can also go through our other suggested articles to learn more –

  1. What is MVC?
  2. Testing Interview Questions
  3. What is Software Testing?
  4. Careers in Software Testing
Popular Course in this category
Software Testing Training (11 Courses, 2 Projects)
  11 Online Courses |  2 Hands-on Projects |  65+ Hours |  Verifiable Certificate of Completion
4.5
Price

View Course

Related Courses

Penetration Testing Training Program (2 Courses)4.9
TestNG Training (4 Courses, 2 Project)4.8
1 Shares
Share
Tweet
Share
Primary Sidebar
Footer
About Us
  • Blog
  • Who is EDUCBA?
  • Sign Up
  • Live Classes
  • Corporate Training
  • Certificate from Top Institutions
  • Contact Us
  • Verifiable Certificate
  • Reviews
  • Terms and Conditions
  • Privacy Policy
  •  
Apps
  • iPhone & iPad
  • Android
Resources
  • Free Courses
  • Java Tutorials
  • Python Tutorials
  • All Tutorials
Certification Courses
  • All Courses
  • Software Development Course - All in One Bundle
  • Become a Python Developer
  • Java Course
  • Become a Selenium Automation Tester
  • Become an IoT Developer
  • ASP.NET Course
  • VB.NET Course
  • PHP Course

ISO 10004:2018 & ISO 9001:2015 Certified

© 2022 - EDUCBA. ALL RIGHTS RESERVED. THE CERTIFICATION NAMES ARE THE TRADEMARKS OF THEIR RESPECTIVE OWNERS.

EDUCBA
Free Software Development Course

C# Programming, Conditional Constructs, Loops, Arrays, OOPS Concept

*Please provide your correct email id. Login details for this Free course will be emailed to you

By signing up, you agree to our Terms of Use and Privacy Policy.

EDUCBA Login

Forgot Password?

By signing up, you agree to our Terms of Use and Privacy Policy.

EDUCBA
Free Software Development Course

Web development, programming languages, Software testing & others

*Please provide your correct email id. Login details for this Free course will be emailed to you

By signing up, you agree to our Terms of Use and Privacy Policy.

EDUCBA

*Please provide your correct email id. Login details for this Free course will be emailed to you

By signing up, you agree to our Terms of Use and Privacy Policy.

Let’s Get Started

By signing up, you agree to our Terms of Use and Privacy Policy.

This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to our Privacy Policy

Loading . . .
Quiz
Question:

Answer:

Quiz Result
Total QuestionsCorrect AnswersWrong AnswersPercentage

Explore 1000+ varieties of Mock tests View more