Software Testing Document

Types of Testing: Unit testing : it is a white box testing conducted by developer. It is used to test most micro scale of testing to test particular function or code modules. Unit : Smallest testable piece of software. Unit testing done to show that the unit doesn’t satisfy the functional specification and /or its implemented structure doesn’t match the intended design structure. Smoke Testing : it is used to test or validate the every basic functionality of the system. Or Smoke Testing :  It is an initial type of testing once testing team gets a build needs to do the BVT (Build verification testing) or smoke testing for verifying the major functional component of the build. This has to be done based on the requirement. Functional Testing : It is used to test each and every module is functionally stable entire module is tested by functional testing. Regression Testing : testing to ensure that code changes have not had an adverse effect to the other module or an existing

Client server application/Web server application Points : It is a network architecture which separates a client from a server. • The client software can send request to a server. • Server includes web server, application server, file server, terminal server and mail server. Ex: if you are browsing an online store, your computer and web browser would be considered a client and the computer, data and application that make up the online store would be considered the server. When your web browser request a particular page from the online store, the server finds all of the information required to display the article in the database, assembles it into a web page and send it back to your web browser for you to look at. Characteristics of a Server : • Passive (slave) • Waits for the request • Upon receipts of request, processes them and then server’s replies. Characteristics of a Client : • Active (master) • Sends request • Waits for and receives server replies Servers are two

Types of Testing Techniques : 1. Equivalence Partitioning 2. Boundary Value Analysis 3. Error Guessing. Equivalence Partitioning : Dividing the input domain into classes of data for which test cases can be generated. Equivalence Class : A portion of a component input or output domain for which the component behavior is assumed to be the same from the component specification. Boundary Value Testing : Boundary Testing : Test which focus on the boundary or limit condition of the software begins tested. Boundary Value Analysis : BVA is similar to equivalence partitioning but focus on “cover –cases”, or values that are usually out of range as defined by the specification. This means that if a function expects all values is range of negative 100 to positive 1000, test input would include negative 101 & positive 1001. Error Guessing : In software testing, error guessing is a test method in which test cases used to find bugs in programs are established based on experience i

Test Matrices: Test matrices accomplish is analyzing the current level of maturity in testing and give a projection on how to go about testing activities by allowing us to set goals and product future trends. Table showed are some examples there are many test matrices. 

Testing Life Cycle: Determine the set of activities performed by tester for testing the software the product life cycle. Software testing life cycle contains following activities’. 1. Test Plan Preparation 2. Test Specification preparation 3. Test Execution 4. Defect Reporting and Tracking Test Drive : A program or test tool used to execute a test. Also know as Test Harness. Test Environment : The hardware and software environment in which test will be run and any other software with which the software under test interacts. Test Procedure : A document providing detailed instruction for the execution of one or more test cases. Test Scripts : Commonly used to refer to the instruction for a particular test that will be carried out by an automated test tool. Test Suite : A collection of tests used to validate the behavior of a product. Test Scenario : TS is a set of action or test cases executed in sequence which represents a business operation. Top down Testing: An ap

Adhoc Testing : Testing is done without any formal test plan or test case creation. It helps tester in learning the application prior starting with any other testing. GUI : GUI testing is done to whether all the GUI standards are followed or not. Microsoft GUI standard are the best standard for GUI. Content: Section I: Windows compliance standards: 1. Application 2. For each window in the application 3. Text boxes 4. Options (Radio buttons) 5. Check boxes 6. Command button 7. Drop down list boxes 8. Combo boxes 9. List boxes Section 2: Tester’s screen validation checklist. 1. Aesthetic condition 2. Validation condition 3. Navigation condition 4. Usability condition 5. Data integrity condition 6. Modes (Editable read only) condition 7. General condition 8. Specific field tests 9. Data field test 10. Numeric field 11. Alpha field check Exploratory Testing : This testing is similar to ad-hoc testing and is done in order to explore the application to find out t

Software Development Life Cycle: The software development life cycle begins with the identification of requirement for software and ends with the formal verification of the development software against that requirement. In V-Shaped model the development and testing phase are carried out parallel sequence i.e. Verification on one side and validation on other side. Advantage : As the verification and validation are done along with the test management. The outcome of V shaped model is a quality product. Drawback : Time consuming and costly model. Water fall model : in this model the development and testing phase are carried out step by step process and a base line document is prepared. Advantage : It’s simple model and easy to maintain, project implementation is very easy. Drawback : Can’t incorporate new changes in the middle of the project development. Base line document. Prototype Model (Rapid Prototype model) :- This is cyclic version of the linear model. In this model once

Manual Testing : It is a process in which all the phase of software testing life cycle like test planning, test development, test execution result analysis, bug tracking and reporting are accomplished successfully normally with human efforts. Testing : An examination of the behavior of a program by executing on sample data sets. OR A Testing is a process of executing a program with the intent of finding bugs, and to improve the quality. Software Testing : The process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies specific requirement or to indentify difference b/w expected and actual result. Purpose of Testing : 1. To uncover hidden errors 2. To achieve the maximum usability of the system 3. To Demonstrate expected performance of the system. General reasons for Defect found in software system are:  It improperly interprets requirements  The users specify the wrong requirement  The requirement are un-c

BUG What is a BUG? A bug is a deviation from the requirement. Or        Bug can be defined as the abnormal behavior of the software. Classification of Bug : Functionality bug Security bug Interface bug Cosmetic bug Guidelines on deciding the severity of bugs : Critical/show stopper: An item that prevents further testing of the product or function under test can be classified as critical bug. No work around is possible for such bugs. Ex. A missing menu option or security permission required to access a function under test. Major/high: A defect that does not function as expected/designed or cause other functionality to fail to meet the requirement can be classified as major bug. The work around can be provided for such bug Ex. Include inaccurate calculation the wrong field being updated. Average/Medium: The defects which don’t conform to standards and conventions can be classified as medium bugs. Easy workaround exists to achieve the funct

 Root Cause Analysis : Root cause analysis forms the techniques or tools that are used to determine the reason for a problems occurring. Schedule Variance : Schedule is the plan for executing a project and variance is the slippage of the test plan. The Root Cause Analysis will be performed by the action listed below: -           Understand the problem -           Gather required information on the cause of the problem. -           Identify all the major and minor issues that create the problem. -           Find the root causes based on the evidence or issues. -           Do recommendations targeting all the issues. -           Implement all the recommendation. The input to the root causes analysis will be a problem and output to the root cause analysis will be the solution that closes all problems. Root Causes Analysis tools types : Based on the problem encounter we choose the tool: 5 Ways : Mostly used with problems involving human factors or interactions. Barrier Analysis :