Manual Testing - Basic Information

MANUAL TESTINGWhat is Testing?Testing is process of evaluating the project/product Testing is act of checking if a product performs as expected Test is kind of specific part of s/w eng. to check the robustness of s/w for various invalid and valid inputs and checking of the output according to the requirement specification and functional specification.Testing: Verification and Validation of an Application.What is Test Plan?test plan is a road map for successful complete testing Test Plan:  When to test?  What to test?  Who is going to test?  How is he going to test?  etc.Write paper which plans in better quality the process of testing. Scope, People needed, Approach, Criteria (pass/fail/suspension/resumption), Environment needs, Deliverables test, Incidental, Risk (contingencies), Schedule (Time/Date), Responsibilities, Short term Objectives (Objectives), Long term Objectives (Aim) What is Test Case?Test case is a action that validate the product success or failureTest case contains Test case IDTest case Description/PurposeTest case Procedure Test DataExpected ResultActual ResultTest Log (Result)Reason If need NoteDifferentiate Between Error, Defect, Bug, and Fault?Error: Occurred in programming side. Developers should identified and rectified the errors (Logical error, Syntax error)Defect: Occurred in testing side. Testers identify the mistakes/wrong in the application. (Testing Term)Bug: Developers also accepts testers defect, its called Bug (Testing Term)Fault: Customer/Client are identified the mistakes in the application after delivering the project/product. What is Defect?The name defect is testing term. Testers identify the mistakes in the application.Expected Result != Actual Result What is Quality?User FriendlyExpected Result = Actual ResultFull fill the user’s requirement and satisfaction. Differentiate between Project and Product based Testing?product Testing is nothing but after preparing the application we will contact to the clients. If client need any changes then we will change it according to requirements. Example : Microsoft (Vista)project based means client only give all the customer requirements. According their requirements we will test the application.Example : TCSSoftware Development Life Cycle (SDLC)Its containPlanAnalysisDesignImplementationOperation and Support (Maintenance) Software Testing Life Cycle (STLC)Test plan preparationTest case preparationTest case executionTest log Defect trackingReport writingTest case Preparation Actual Result are meet to customer expectation. Contains Test case IDTest case DescriptionTest case ProcedureTest case DataExpected ResultTestcase ExecutionActual Result What we actually got in the application.Test LogPass or Fail Expected Result = Actual Result ------- Pass Expected Result 1= Actual Result ------ FailTestcase Sample: testcase idtest case proceduretest case desctest stepstest status (P/F)Notes (if need)stepexpectedactualDefect TrackingContainsTest case IDDefect IDDefect DescriptionDefect StatusPrioritySeverity3) Defect Status (Bug Life Cycle) ContainsUnconfirmedNewAssignedOpenIn progressResolved FixedWon’t FixedDuplicateIncompleteCannot ReproduceReopenClosedUnconfirmedIt means Testers identify a defect but not confirm whether it’s a defect or not (Like Look and Feel) NewMeans testers confirm the defect in the application. AssignedAssign a person (Developer) to rectify the defect.OpenThe issue is open and ready for the assignee to start work on it.In progressThis issue is being actively worked on at the moment by the assignee.ResolvedResolve the bug by developers (also tester’s side)FixedRectify the issues what the testers raiseWon’t FixThe problem described is an issue which will never be fixed.DuplicateThe problem is a duplicate of an existing issue.IncompleteThe problem is not completely described.Cannot ReproduceAll attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.ReopenedThis issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.ClosedThe issue is considered finished, the resolution is correct. Issues which are closed can be reopened.Manual Testing Life Cycle Developer develop (Build) the application and send it to testers. Testers test the application, if there is any defect occur they prepare a test report and send it to developers and the developers are to open and rectify the defect, and resend it to tester.. This process continues up to the product/project are defect free or quality.Testing PhaseTaskTesting.RolesTest Engineer.ProcessFirst of all the Test Engineer will receive the requirement documents and review it for under studying the requirements.If at all they get any doubts while understanding the requirements they will prepare the Review Report (RR) with all the list of doubts.Once the clarifications are given and after understanding the requirements clearly they will take the test case template and write the test cases.Once the build is released they will execute the test cases.After executions if at all find any defects then they will list out them in a defect profile document.Then they will send defect profile to the developers and wait for the next build.Once the next build is released they will once again execute the test casesIf they find any defects they will follow the above procedure again and again till the product is defect free.Once they feel product is defect free they will stop the process.ProofThe proof of this phase is Quality Product.Test caseTest case is an idea of a Test Engineer based on the requirement to test a particular feature.TESTING METHODOLOGY (OR) TESTING TECHNIQUESThere are 3 methods are thereBlack Box Testing.White Box Testing.Gray Box Testing1) Black Box TestingIt is a method of testing in which one will perform testing only on the functional part of an application without having any structural knowledge. Usually test engineers perform it.2) White box Testing (Or) Glass box Testing (Or) Clear box TestingIt is a method of testing in which one will perform testing on the structural part of an application. Usually developers are white box testers perform it.3) Gray box TestingIt is a method of testing in which one will perform testing on both the functional part as well as the structural part of an application.LEVELS OF TESTINGThere are 5 levels of testing.Unit level testingModule level testingIntegration level testingSystem level testingUser acceptance level testing1) Unit level testingIf one performs testing on a unit then that level of testing is known as unit level testing. It is white box testing usually developers perform it.Unit: -It is defined as a smallest part of an application.2) Module level testingIf one perform testing on a module that is known as module level testing. It is black box testing usually test engineers perform it.3) Integration level testingOnce the modules are developing the developers will develop some interfaces and integrate the module with the help of those interfaces while integration they will check whether the interfaces are working fine or not. It is a white box testing and usually developers or white box testers perform it.4) System level testingOnce the application is deployed into the environment then if one performs testing on the system it is known as system level testing it is a black box testing and usually done by the test engineers.5) User acceptance testing.The same system testing done in the presents of the user is known as user acceptance testing. It s a black box testing usually done by the Test engineers.Testing TypesAd hoc testingTesting carried out using no recognised test case design technique.Boundary value testingA testing technique using input values at, just below, and just above, the defined limits of aninput domain; and with input values causing outputs to be at, just below, and just above, thedefined limits of an output domain.Regression testingRetesting of a previously tested program following modification to ensure that faults have notbeen introduced or uncovered as a result of the changes made.Stress testingTesting in which a system is subjected to unrealistically harsh inputs or load with inadequateresources with the intention of breaking it.