Skip to main content

What is Software Testing?

Software testing is a process of executing a program or application with the intent of finding the software bugs.
  • It can also be stated as the process of validating and verifying that a software program or application or product:
    • Meets the business and technical requirements that guided it’s design and development
    • Works as expected
    • Can be implemented with the same characteristic.
Let’s break the definition of Software testing into the following parts:
1)  Process:  Testing is a process rather than a single activity.
2)  All Life Cycle Activities: Testing is a process that’s take place throughout the Software Development Life Cycle (SDLC).
  • The process of designing tests early in the life cycle can help to prevent defects from being introduced in the code. Sometimes it’s referred as “verifying the test basis via the test design”.
  • The test basis includes documents such as the requirements and design specifications.
3)  Static Testing:  It can test and find defects without executing code. Static Testing is done during verification process. This testing includes reviewing of the documents (including source code) and static analysis. This is useful and cost effective way of testing.  For example: reviewing, walkthrough, inspection, etc.
4)  Dynamic Testing:  In dynamic testing the software code is executed to demonstrate the result of running tests. It’s done during validation process. For example: unit testing, integration testing, system testing, etc.
 5)  Planning:  We need to plan as what we want to do. We control the test activities, we report on testing progress and the status of the software under test.
6)  Preparation:  We need to choose what testing we will do, by selecting test conditions and designing test cases.
7)  Evaluation:  During evaluation we must check the results and evaluate the software under test and the completion criteria, which helps us to decide whether we have finished testing and whether the software product has passed the tests.

8)  Software products and related work products:  Along with the testing of code the testing of requirement and design specifications and also the related documents like operation, user and training material is equally important.


Comments

Popular posts from this blog

Software Testing Documents

Software Testing Documents- I) Test Policy (Company Level Document) 1) Test Definition              (Verification & Validation) 2) Testing Process (Proper planning before starts testing) 3) Testing Standards 4) Testing Measurements (QAM, TTM, PCM) 5) Risks 6) Approvals 7) Comments 8) Revision History -------------------------------------------------------- II) Test Strategy (Company Level Document) Table of Contents 1.0    Introduction 2.0    Objective 3.0    Scope of the Document 4.0    Test Approach 4.1              Introduction 4.2              Functional and Usability Issues 5.0        Phases of Testing 5.1        ...

Introduction to Apache JMeter

Apache JMeter is a great open source application with awesome testing abilities. Web Server is a platform which carries loads of numbers of applications and users, so that it is necessary to know that how does it works or performs means; how effective it is to handle simultaneous users or applications. For example; how the “Gmail” supporting server will perform when numbers of users simultaneous access the Gmail account – basically have to do performance testing using performance testing tools like JMeter, Loadrunner etc. To check the high performance of the application or server, do high performance testing using JMeter for exceptional results. Before understanding Overview of JMeter , let us have a look on three testing approach, Performance Test : This test provides the best possible performance of the system or application under a given configuration of infrastructure. Very fast, it also highlights the change need to be made before application goes into prod...

Testing Artifacts

TEST PLAN Fundamentals TEST PLAN DEFINITION A Software Test Plan is a document describing the testing scope and activities. It is the basis for formally testing any software/product in a project. ISTQB Definition test plan : A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice,and any risks requiring contingency planning. It is a record of the test planning process. master test plan : A test plan that typically addresses multiple test levels. phase test plan : A test plan that typically addresses one test phase. TEST PLAN TYPES One can have the following types of test plans: Master Test Plan: A single high-level te...