Testers View

  Software development life cycle The SDLC Life Cycle, or just the SDLC as it’s known, is the process of developing software to meet a need or solve a problem. This life cycle involves quite a few steps. Planning The first stage of any project is the planning stage. In the Software Development Life Cycle (SDLC), this is where the appropriate people discuss the goals of the project, and how to run the project. A project needs to be planned before it starts. This ensures it is well run and achieves the goals that it is supposed to. It doesn’t matter if it’s a slight change to a website, or a large system being implemented, there is some level of planning done at the start of the project. Roles involved : Project Manager, Project Sponsor, other business representatives Analysis      Majority of the investigation is done in this phase, where the analysis is done to find out what the business problem is, what the detailed targets are, what the so...

Business requirement document: This document contains the client requirements in high level.These requirements can be one-liner, a statement or user stories, It depends on the client. Business analyst use some requirement Gathering Techniques like Questionnaires, One-One Interviews, Group Discussions etc to design this document. This document generally does not have solution for the requirement in it.  This document answers what the business or the client requires from our side to be done. Functional requirement document: In general this document is prepared once the Business requirement document is being mutually accepted by both the sides(Client and the business analyst). Functional requirement document is designed with solution and the workflow to achieve the business requirements in terms of the product’s intended capabilities, look and feel, and User interface. This document is mainly targ...

1.Requirement analysis: A feasible study on the business requirement and understanding the software requirements. Establish the environment requirements. Prepare the higher level test plan including the risk and tools used in the project. Establish defect tracking methodology. Identify the type of the testing to be carried in the project. 2.Design: Prepare the Data Flow Diagram (DFD) of the project and document it. Verify the flow of the functionalities. Since, QA reviews the design as an end user's perspective. Verify the user type and the user interface/experience. Prepare the low-level test plan including risk, scope, tools, environment etc. 3.Development: Develop the test case so that it can be used in TDD or BDD. Preparation of Environment for testing. 4.Testing: Execute the test case.  Finding the defect and report them as early as possible. Verify the bugs are fixed before release Perform the following testing and assure that no d...