Saturday, 20 December 2014

Manual Testing is a Base to Play on Technology Tools – A Learning Guide

As we all are familiar with a fact related to one of IT sector's concept that software testing is a set of technical activities and functions that are used to detect errors and improve the quality of an application system. For this goal, we basically select two ways to improve the quality as well as reliability of software system – Manual & Automation. On the other hand, nowadays, aspirants who wish to start their career in quality area, want to begin with test automation, which has become a hot topic in this industry. However, according to me, manual testing is base to help in learning automation testing properly. They can take manual testing training from a reputed institute by taking admission in manual testing course, in order to achieve their career objectives. So what exactly manual testing is and which concepts are covered in it...I will be discussing all these things right here...

Before starting discussing the manual testing concept, I want to share an important point with you so that you can accomplish your software testing goal in an easy way by learning all the technicalities related to this industry. QACampus is a leading manual testing training institute that provide extensive knowledge of software testing and best training to aspirants who want to become a successful tester. It offers different training packages that are helpful to them in order to accomplish the career goal.

What is Manual Testing?

A manual process carried out to find errors from software system is known as manual testing. Through this method, a tester plays an important role as an end user and verify all the features of program for ensuring smooth behavior of an application. Being a basic type of software testing, it helps to detect bugs or errors in software under test process. A tester creates the test plan and follow it to ensure the comprehensiveness of testing while executing the test cases manually.

What is the Goal of Manual Testing?

The main objective of manual testing is to make sure that software under test is error free and is working as per the requirement specification document. It doesn't use any automated tool during the entire testing process as everything is performed on manually basis.

As we know manual testing is a vast concept in IT industry so we deal with many terms everyday in order to take the testing process in a smooth way. Here I will try to underline some common and useful things that are absolutely required to make one solid base in manual testing.

  • Integration Testing: Integrating testing is performed to check links of modules and functionality and exchange data between modules. Also, it helps in flowing of control in software.
  • Bug Life Cycle: This concept of manual testing begins from “New” stage then it comes in “Open” stage. After resolving the issue in an application, it comes in “Resolve” stage. After this, it comes in “Fixed” stage, if it is working in staging environment.
  • Test Plan: Test plan describe the process of testing document by defining – how the testing will be performed, what quality level is required, who will do it, how long the testing process will take and what will be tested.
  • Regression Testing: in regression testing, system is checked thoroughly and whether effect of testing process is there on the system is also checked.
  • Severity & Priority Levels: P1, P2, P3, P4 (Priority Levels); Cosmetic, Minor, Normal, Major, Critical, Blocker (Severity Levels)
  • Severity: Severity is defined as it has blocker condition for software.
  • BVA: It is the method of dividing software system into segments so that testing can occur within the boundaries of those segments.
  • Priority: It means that this software testing concept has critical condition for current deliverable.
  • Types of Integration Testing: Bottom-Up and Top-Down
  • Test Life Cycle: A test life cycle is a cycle of testing activities that get started from plan test and before writing test cases.
  • Traceability Matrix: A traceability matrix is basically a document that is defined as the relationship between test requirements & test case.
May be in this post, all topics related to manual testing are not covered but I will always update my knowledge in the upcoming posts!