Introduction to Software Testing

-
What is Software Testing?
Software testing is a process of executing a program or application with the intent of finding the
software bugs.
Authors Rex Black, Erik Van Veenendaal & Dorothy Graham in book “Foundations of Software
Testing, ISTQB Certification” have defined testing as “Testing is a process that consists of all
lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation
of software products and related work products to determine that they satisfy specified
requirements, to demonstrate that they are fit for purpose and detect defects.”
--Foundations of Software Testing, ISTQB Certification

Based on the above definition software testing can be explained as the process of validating and
verifying a software program or application or product that: -
Meets the business and technical requirements that guided the expected design and
development
Functionalities of every modules work as expected
Deliver the best possible software program or application to the stakeholders free of bugs
as much as possible. It is true that, no software or application is hundred percent bug free,
but every effort should be employed to make sure bugs those can impact the users in
regards to business process must be fixed before the software is released in production.
Software testing plays very important role in developing any software program or application,
from initial coding stage to release of such software program or application. Therefore, it is
obvious that: -

Testing is a Process: Testing is a continuous process rather than a single activity.
Testing is an Integral part of SDLC: Testing is involved throughout the Software
Development Life Cycle (SDLC).
Testing gives software ultimate confidence: Once testing is completed stakeholders
understand and can make decision whether the software gets a GO status or NO GO
status, meaning depending on the existence of high priority to low priority defects in the
software on a certain stage management can predict the coherent risks involved in
releasing such software program or application.

Comments

  1. UnknownAugust 12, 2017 at 8:14 AM

    Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test.[1] Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include the process of executing a program or application with the intent of finding software bugs (errors or other defects), and verifying that the software product is fit for use.

    Testing is required for an effective performance of software application or product. It's important to ensure that the application should not result into any failures because it can be very expensive in the future or in the later stages of the development. It's required to stay in the business. so it's not wasting money but saving!

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Create an Issue in JIRA (2)

-
Creating issues and sub-tasks The building blocks of any project are issues. Issues act as the packets of work that travel through their respective workflows within their projects, until the work is completed. An issue may also have sub-tasks that can be assigned and tracked individually, as well as issue level security to restrict the issue to select members of your team. On this page, you'll learn more about creating and converting issues and sub-tasks, and setting issue level security. If you are looking to import multiple issues (and sub-tasks) using a CSV file, you can find the import process explained in more detail  here . Before you begin You need the  Create Issue  project permission for the issue's relevant project. Creating an issue Click  Create  at the top of the screen to open the  Create Issue  dialog box. Select the relevant  Project  and  Issue Type  in the  Create Issue  dialog box...
Read more

Fundamentals of Accessibility Testing ... 2

-
  When you are playing the role of Accessibility tester, you're not only helping the Stakeholders to be 508 compliant on their Web Application or any other Digital Media/ Technology but also you are helping a huge group of people who, otherwise wouldn't be able to use these Web Application or Digital Media/ Technology. Following points are to be considered very important when you are engaged in 508 Testing AKA Accessibility Testing: Whether an application provides keyboard equivalents for all mouse operations and windows? Whether tabs are logically ordered to ensure smooth navigation? Whether shortcut keys are provided for menus? Whether response time of each screen or page is clearly mentioned so that End Users know how long to wait?   Whether all labels are written correctly in the application? Whether color of the application is flexible for all users? Whether images or icons are used appropriately, so it's easily understood by the end users? Whether an application has a...
Read more