Software testing is a process where a software tester/team runs a program or a system to find bugs or defects, to maintain the correctness and reliability of a program. Software testing also validates and verifies the program to check if the business and technical requirements are met, and is working as expected.
Step by Step tutorials to Learn Software Testing
Is Software Testing a right career choice? How is software testing as a career? What opportunities do I have. Check this article to know more.
Difference between Quality Assurance (QA) and Quality Control (QC) In IT industry, people often confuse quality assurance with quality control. This article will differentiate Quality Assurance and Quality control.
Learn the pros and cons of manual and automated testing. This article will tackle the differences between manual and automated testing, their pros and cons, and when to perform manual or automated testing.
It has not been proven that developers who build and code the program can substitute a tester and follow a detailed test plan. As they say, “Good Developers may not be Good Testers”. Following are the pros and cons if the developer will test their own program.
Software Development Life Cycle (SDLC) provides a planned and standardized process for all phases of any System Development stage. Each phase tracks the development of the system, from project planning or feasibility study to maintenance of the system.
Black-box and white-box testing are commonly used on numerous testing techniques. In this article, we will tackle the use and the techniques of testing for the two.
Documentation is writing narrative information about data processing activities that was developed and maintained. In software testing, documentation may include writing…
Check the exhaustive list of frequently asked software testing interview questions
List of frequently asked software testing interview questions. How to deal with non-reproducible bugs?What are the common misconceptions about Software Testing?
What do you think is the best strategy to apply if there isn’t enough time for testing?At what stage does User Acceptance Testing come into picture on software testing?When will we know that testing is complete?How to ensure that a bug has been fixed? Get answers to all such questions and more
Here are the tools you can use to report your software testing activities. Pareto Chart, Fish Bone Diagram, Histograms, checksheets.
Test Reporting tools used in software testing. Run Charts, Regression Analysis, Control Charts, Scatter plot diagrams
Software Requirement Specification (SRS) document serves as a means of communication between the client (user) and developer because it defines the “what” and “how” of a software project. It contains the purpose, functionality, design, constraint and behavior of the software in which it details how the software should be implemented. SRS should be written in simple and exact language for the client and developer to easily understand and be able to develop the software correctly.
A test case is a set of procedures, conditions, executions, and expected results verifying the software compliance with the requirements. Writing a test case covers the objective of the test case, conditions, steps to perform, necessary inputs, expected result, actual result and notes from the tester.
The primary goal of any tester is to detect as many bugs as possible irrespective of the techniques (s)he uses. Once a bug has been found, a tester is required to submit a bug report. Hence, a bug report should be well documented. Make it easy and clear to let the developer know the exact failure of the software.
Exploratory testing – a term coined by Cem Kaner – is a software testing method that implements learning, test design, and test execution at the same time simply because you explore while testing. It really doesn’t follow a set of procedures, scripts or standards that is why it is mistakenly known as the “do it yourself” or careless activity, which is in fact, this approach describes an intellectual testing.
Once there is a change or update being requested by the users, one of the test management activities being used is the Software Configuration Management.
In verification, testers ensure that the system meets the organization’s standards and processes, and answers the question “Did we build the right system?” In validation, testers physically ensure that the system has met all business and user requirements, and that the features and functionalities are working as designed.
Sanity testing is a brief testing of major functionalities of software based on specifications, requirements, and features. Smoke testing is a quick-and-dirty run through the major functionalities of the software without bothering with details and functionalities.
The two most renowned software testing certifications are CSTE and ISEB/ISTBQ. In this series of articles we will tackle the general information about CSTE and ISEB/ISTBQ Certifications. What is CSTE?