Manual Testing complete

  • Published on
    28-Dec-2015

  • View
    15

  • Download
    0

Embed Size (px)

DESCRIPTION

Manual Testing complete

Transcript

<p>Manual Testing</p> <p>Quality: Quality is defined as justification of all client requirements of a project/product &amp; deliver the application in time without having any defects is called Quality.</p> <p>Quality Assurance: Quality Assurance is the process to verify all the standards and process of a company for giving the right product to the client.</p> <p>Quality Control: Quality Assurance is the process to verify all the standards and process of a company for giving the right product to the client.</p> <p>Software: Software is a set of Programs, set of logic &amp; related data that gives instructions to the system, what to do &amp; how to do. </p> <p>(Or) A set of executable programs is called software. We have 2 types of Software:</p> <p>1. Product</p> <p> 2. Project1. Product: Product is something which is developing for segment of customers. There is no end of developing &amp; testing activities in the product, because the product will release into the market versions by versions. E.g.: Operating system, MS office, Photoshop &amp; Processors Etc.2. Project: Project is something which is developing for only specific customers. There is end of developing &amp; testing activities in the project, because whenever we satisfying the client requirements we need to stop the developing &amp; testing activities. E.g.: Manufacturing application, Hospital management application, etc</p> <p>In Each &amp; every Project/Product development we have 2 different teams. </p> <p>1. Development Team</p> <p> 2. Testing Team</p> <p> 1. Development Team: The responsibility of Development Team has to develop the Application project/ product according to the client requirements. 2. Testing Team: The responsibility of Testing Team has to Test the developed Application (Project/Product) by using different Testing Types &amp; Techniques according to the client requirements.</p> <p>Testing: Testing is the Verification &amp; Validation to ensure to deliver the defect free Application/Product to the client. </p> <p>(Or)Software Testing: Testing is a process of executing a program with the intent of finding errors.</p> <p>(Or)</p> <p>Perform the testing on the software application or product is called Software Testing.</p> <p>We have 2 different types of Testing under Software Testing.</p> <p>1. Manual Testing</p> <p>2. Automation testing </p> <p>1. Manual Testing: Perform the Testing on the Application/Product with human interaction is called Manual Testing.2. Automation Testing: Perform the Testing on the Application/Product with the help of some Third party tools like QTP, Selenium, Load runner etc. is called an Automation Testing.</p> <p>In both Manual Testing &amp; Automation Testing we are performing same testing in the application, but the way is different while we are performing the testing in Manual Testing &amp; Automation Testing.</p> <p>Why Testing is required in Software? (Or) What is meant by Quality Software?1. Maintain the quality of the application.2. Identify the defects and solved the defects before release the application to the clients without having any defects in the application.3. Meet the client requirements (Functionality). 4. Meet the client expectations (Performance, Usability, Compatibility, Security ) 5. Time to release.What are Testing objectives? 1. To find out the difference b/w customer Expected values &amp; Actual values. 2. To find out the errors, which are unidentified by the development team during developing the application.3. Whether the application is working or not according to the company standards.</p> <p>Client: Client is a person who is providing the requirements to the company for developing their business application is called client.</p> <p>Company: Company is an organization which is developing the application according to the client requirements is called company.</p> <p>End User: End user is a person who is using the application in the final stage is called an End user. E.g.: Infosys has developed an online application for SBI Bank. Here SBI Bank is a client to Infosys Company and End user will be customers of SBI Bank. </p> <p>Difference between Defect, bug &amp; error?Defect: While executing the test cases, if we found any issues then the issues is called defect.Bug: Once the developer accepts our defect, then it is called as bug. Error: It may be program error or syntax error.Software biddingA proposal to develop the software is called software bidding.Software Development Life Cycle (SDLC) SDLC is the process which we are following to complete the software project/product development activities that includes both Development &amp; Testing Activities.</p> <p>1. Requirements:</p> <p>Requirements is the first phase of SDLC. Once the project has been confirmed between client &amp; company. Client will provide the requirements to the company. Client always provides the requirements in their business prospective. In this phase BA (Business Analyst) will be involving to collect the requirements from the client. For collect the requirements from the client, BA will following below approaches.</p> <p> 1. Questionnaire 2. KT-Knowledge Transfer 3. Walkthrough 4. Inspection</p> <p>1. Questionnaire: By using this approach BA will collect the requirements from the client by asking the questions to the clients.</p> <p>2. KT-Knowledge Transfer: In this approach client will provide KT-Sessions to the BA for understand the requirements.</p> <p>3. Walkthrough: In this approach BA will go through the requirements documents which has provided by the client and understand the requirements.</p> <p>4. Inspection: In this approach BA will collect the requirements from the clients by inspecting the client business location directly.</p> <p>2. Analysis: In Analysis phase, BA will be involving to analyze the requirements and BA will design the documents as understandable format of the requirement documents called Use case/BRS doc.BRS doc: BRS doc divided into 2 docs.</p> <p> 1. SRS 2. FRSSRS doc: SRS doc contains details about software &amp; hardware requirement.FRS doc: FRS doc contains details about the functionality of the project.Use case Doc: Use case doc is in the format of word doc. One use case doc contains one flow of requirements.</p> <p>3. Design: In designing phase, system architecture will be involving to design the architecture of the application.There are 2 types of Designs 1. HLD (High Level Design): It defines overall architecture of the application that includes all the modules in the application.</p> <p> 2. LLD (Low Level Design): It defines overall architecture of the individual modules that includes all the sub modules &amp; screens of the application.* Most of the projects are using UML for designing the architecture of the application.4. Coding: In coding phase, development team will be involving to write the code for the functionality of the individual module. After completion of all individual modules, the development team will be integrate all the modules and make it as a single application.</p> <p>5. Testing: In testing phase, Testing Team will be involving to perform the testing on the application based on the client requirements. While testing the application testing team will execute the test cases, using different types of testing &amp; techniques.</p> <p>6. Release/Maintenance/Production: In this phase, Technical People will be involving to deploy the application into production environment.</p> <p>Types of Testingwe have 2 types of Testing.1. Functional Testing </p> <p> 2. Non Functional Testing1. Functional Testing: Testing the application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.Unit TestingIn Unit testing, development team will be involving to perform the testing on individual module of the project through a set of white box testing techniques is called Unit testing/Module/Component Testing.</p> <p>Integration Testing (Top Down, Bottom up Testing)</p> <p> In Integration Testing, development team &amp; testing team will be involving to perform the testing on the application. During Integration Testing we are verifying the data flow between all the modules in the application is working or not. Because every individual module is working fine but after integrates all the module &amp; make it as single application that application may or may not work.Approaches in Integration Testing1. Top-Down Approach2. Bottom-Up Approach3. Sandwich Approach4. Big bang Approach</p> <p>1. Top-Down Approach If all main modules are developed and some of the sub modules were not developed in a project. In that case programmers need to create some temporary programs called Stubs. Which acting as a sub module.2. Bottom-Up Approach If all sub modules are developed and some of the main modules were not developed in a project. In that case programmers need to create are creating some temporary programs called Drivers. Which acting as a main module.</p> <p>3. Sandwich Approach If some of the Main modules &amp; some of the sub modules were not developed in a project. In that case programmers need to create some temporary programs called drivers &amp; stubs. Which acting as a main modules &amp; sub modules.</p> <p>4. Big bang Approach Whenever all the modules are developed then integrate all the modules &amp; make it as a single application is called Big bang approach.Types of Testing</p> <p>Sanity Testing After receiving initial build, Testing Engineers validating the major functionalities of the application whether it is working or not. If major functionalities of the application is working fine then we can perform further testing of the application. If major functionalities of the application is not working fine then we cant move further testing. So we can reject the build. </p> <p>Smoke Testing Validating the major functionality of the application by the development team in development environment is called smoke testing.Note: Definition wise both Sanity &amp; Smoke testing is different. But practical oriented is same.</p> <p>Usability Testing/User Interface Testing/GUI Testing Verifying the user friendliness of the application in terms of colors, logos, fonts, alignments etc. is called Usability Testing. ( Ease of use (Understandable to users to operate) ( Look &amp; Feel (Pleasantness or attractive screens) ( Speed of interface (Less no. of events to complete the task)Usability Test Scenarios: Web page content should be correct without any spelling or grammatical errors All fonts should be same as per the requirements.</p> <p> All the text should be properly aligned.</p> <p> All the error messages should be correct without any spelling or grammatical errors and the error message should match with the field label.</p> <p> Tool tip text should be there for every field.</p> <p> All the fields should be properly aligned.</p> <p> Enough space should be provided between field labels, columns, rows, and error messages.</p> <p> All the buttons should be in a standard format and size.</p> <p> Home link should be there on every single page.</p> <p> Disabled fields should be grayed out.</p> <p> Check for broken links and images.</p> <p> Confirmation message should be displayed for any kind of update and delete operation.</p> <p> Check the site on different resolutions (640 x 480, 600x800 etc.?)</p> <p> Check the end user can run the system without frustration.</p> <p> Check the tab should work properly.</p> <p> Scroll bar should appear only if required.</p> <p> If there is an error message on submit, the information filled by the user should be there.</p> <p> Title should display on each web page</p> <p> All fields (Textbox, dropdown, radio button etc) and buttons should be accessible by keyboard shortcuts and the user should be able to perform all operations by using keyboard.</p> <p> Check if the dropdown data is not truncated due to the field size and also check whether the data is hardcoded or managed via administrator.</p> <p>Functional Testing Validating the overall functionality of the application includes the major functionality with respect to the clients business requirements is called functional testing.</p> <p>Functionality or Requirements testing has following coverage:</p> <p> Control Flow or Behavioral Coverage (Object Properties Checking).</p> <p> Input Domain Coverage (Correctness of Size and Type of every I/O Object).</p> <p> Error Handling Coverage (Preventing negative navigation).</p> <p> Calculations Coverage (correctness of o/p values).</p> <p> Backend Coverage (Data Validation &amp; Data Integrity of database tables). </p> <p> Service Levels (Order of functionality or services).</p> <p> Successful Functionality (Combination of above all).</p> <p>Behavioral Testing/GUI Testing/Control Flow Testing In Control Flow Testing, we are validate each &amp; every object in the application whether the screens are responding correctly or not, while operating on those objects in the screens. </p> <p>Input Domain Testing: In Input Domain Testing, we are using boundary value analysis &amp; equivalence class partition techniques to validate the size &amp; type of each &amp; every input object in the application. Boundary Value analysis: </p> <p>Boundary values are used for testing the size and range of an object. </p> <p>Equivalence Class Partitions: </p> <p>Equivalence classes are used for testing the type of the object. </p> <p>Error handling Testing In Error handling Testing, we are validating each &amp; every screen in the application by giving invalid data to the objects to get error messages or not when user given the invalid data. </p> <p>Calculation Coverage Testing In Calculation Testing, We are validate on the calculation part in the application by giving the valid data to the objects to get the correct output values or not when user given the valid data.</p> <p>Functional Test Scenarios: Test all the mandatory fields should be validated.</p> <p> Test the system should not display the error message for optional fields.</p> <p> Test the numeric fields should not accept the alphabets and proper error message should display.</p> <p> Test for negative numbers if allowed for numeric fields.</p> <p> Test the max length of every field to ensure the data is not truncated.</p> <p> Test the pop up message (This field is limited to 500 characters) should display if the data reaches the maximum size of the field.</p> <p> Test that a confirmation message should display for update and delete operations.</p> <p> Test the amount values should display in currency format.</p> <p> Test the timeout functionality.</p> <p> Test the functionality of the buttons available</p> <p> Test the Privacy Policy &amp; FAQ is clearly defined and should be available for users.</p> <p> Test if any functionality fails the user gets redirected to the custom error page.</p> <p> Test all the uploaded documents are opened properly.</p> <p> Test the user should be able to download the uploaded files.</p> <p> Test the email functionality of the system.</p> <p> Test the java script is properly working in different browsers (IE, Firefox, Chrome, safari and Opera).</p> <p> Test to see what happens if a user deletes...</p>