Software Testing Experts

Test Strategy document is the high level document which is defined the  Software Testing Approach   and  designed by the Project Manager. Test Strategy document derived from the Business Requirement and Specification Requirement.  This document is static document and can't change too often. Once Project Manager develop the Test Strategy then this strategy generally company used for several project. If Software is small then Test Strategy is the part of Test Plan otherwise Test Strategy document should be separated for big projects. Test Strategy document describe the Testing Approach following by the Testing team. Following are the parts of the Test Strategy.

Test Plan is the document describing the scope of the software, approaches that will be used to develop the software, resources which are available and schedule to perform these testing activities.  Test Plan is the document which helpful for all the team member ( it may be Test Team, Developer Team, Business Team or even Customers) to understand the software. Test plan is the document which determine the efforts that team used to work over the software. A Test Plan document is a strategy that will be used to verify that the software meets their design specification and other requirement . A Test Plan is prepared by the Test Engineers.

The basic definition of Test Scenario is what is to be tested. Test Scenario is the hypothetical story to think about the complex system. Test Scenario is differ from Test Cases because in Test Case only single step occur while on Test Scenario multiple steps are combined together. Each Test Scenario contains many Test Cases so we can can say that after Test Cases, we think about Test Scenario. Test cases are derived from Test Scenario while Test Scenario derived from used cases. The ideal Test Scenario is credible, complex, compelling or motivating story and outcome which is easy to evaluate.

Here in this article i am telling you the Test cases of Login page which you can use in your interviews. For Test Cases i am showing you a login page of Google as a sample login form to understand these test cases. Image Source Google

Test cases is the document that contains the information regarding the Test data, Prerequisite, Expected result etc. These test cases developer by the QA Team before develop the code. After develop the code , QA team verified these test cases with the execution of code and as per the output match that with expected result and provide the status of that test Pass or Fail. Test Case document include all possible Test cases by understand the Requirement Document, Design Document. Only your test cases will define the quality of the software. if Test cases include all possible scenario then it is easy to test the application and find bugs and provide good quality of the Software.

In terms of testing both terms looks same and generally people get confused when interviewer ask them to differentiate. These terms are totally different and the people who is leaning testing should know about the difference because this is the common question asked in the interviews. 

High Level Design Document: HLD is the design document convert the user requirement into the detailed design of Application. In HLD document, application is divides into different different modules. After that each modules divides into micro modules and then each micro modules take at a time to work over it. This document include the System Architecture, Database Architecture, Structure of the System, Application Architecture, Application flow, Technology Architecture

V model is the extension of the Waterfall model in which testing phase came along with the Business Requirement Phase and go parallel with every phase of software development life cycle so that if any bug occur in any phase, that bug can be solve in that phase will reduce cost and time to fix any bug.

As per name suggested waterfall model work as the flow of water from top to bottom.  Let me discuss all phases one by one of waterfall model. Requirement Analysis: In This phase, Team will go through the review meeting, Client Discussion, Team Discussion, review existing product, review the client references and go through the client requirement  to understand the client need. In this part Business team will involve with the client. All requirement is gathered in this phase and prepared a document which will help team to proceed over the software. 

Bug life cycle is a cycle of a Bug from when it is generated to when it is closed. Following phases of Bug life Cycle New : When QA team find a new bug we provide 'New' status for that Bug. Open: When QA team add that Bug and Team lead approve the bug to genuine then status of that bug is 'OPEN'

STLC indicate the flow of testing phases that how we will start our testing, what resources we used, what are test plans, what are test cases and the reports. There are some steps of Software Testing Life Cycle. Image Source Google Project Initiation: This is first part of project and collect all information with the interaction with the client, view all existing information, old software to gather information to initiate the project.  System Study: In This past, QA team study regarding the ER , SRS , Use Case, Design part.  Test Plan : Test Planning is most important phase of STLC. Basically as per testing, this is the first phase of STLC. In this phase , Testing team consider all available resources and the activities to achieve the objective of the software. Also team management consider the efforts and cost of the project. This phase also called test Strategy Phase. In this phase we also identify the scope of the Project....

Sometimes in interview this question arise and generally they ask regarding the phases of Software Development model so i am just presenting a Brief idea regarding the SDLC. There are many approaches which used in software Development like Waterfall Model , Incremental Model, V Model , Iterative Model, Spiral Model, Big Bang Model etc. SDLC have following steps: 1) Requirement Analysis: In this phase, Development Team work on gathering the information as much as possible regarding the software. For gathering the information team arrange the meeting with the client, review old sites regarding that work, Team internal Meeting to understand the requirement. 2) System design: In this Phase, Developer plan the System Architecture. System design includes the Scope of Project, Scheduling Plan, Resource Availability, Limitation of the Software, What's new in learning phase, impact over the personal and professional and the end users and the requirement of hardware and software. ...

There are total 7 principles of Testing. Testing Shows the Presence of Bugs: Testing is the process to find the defect but after 100% testing we can't ensure that our application is error free.   We can't sure if tester is unable to find any error in the application then that application is error free.  Exhaustive Testing is impossible: For any application, we can test the application with limited inputs and verify the limited output. It is not possible to test any application with all possible inputs so that we can priorities our test data to cover maximum possibility of error. Suppose for any example you are checking any text box which accept any number only so it is not possible as a tester to check that text box with each possible number so tester can check this with some rule to divide all possible data in different group like tester can check with -ve values, 0, + ve values and any big data like 5653636555565 to check the database limit.  Early Test...

Static Testing and Dynamic Testing Static Testing: Static Testing also called Verification . Under this testing technique, code is not executed. In this technique, user just manually code walkthroughs, test documentation review, review the requirement document and design document to find the errors. Static Testing is more cost effective because this testing is done in the very early phase of software development life cycle so it reduce the cost multiplication to find the errors in early phase. If there is any error in the document then the software will develop same as document . This will increase the cost to fix this issue in later stage so Static Testing is cost effective.

There are various type of Software Testing. Here i am provide you brief idea regarding these software testing type. Later i will provide you detailed description for your understanding. Here i am listing all the type because you can find all definition in one page and it is easy for you guys to compare all the types.

Quality Assurance (QA) and Quality Control(QC) both seems similar for people but they are totally different in Product development cycle. QA and QC both have absolute different role. Generally it is assume that both can interchange their role when needed but this is totally wrong, both role are totally different and not changeable.

SRS is the detailed description regarding the discussion with client as per the requirement. It include the complete process that how the product will flow, what kind of technology we will use to develop the software, what are the strategy we follow. basically SRS is the complete document that help the Developer, Manager, QA Manager and all other user who are taking part to develop the software.

Software Testing is important because the product should be correct, complete and should have the good quality for the end users who access that product. Software Testing always matches the output of the product with the expected output. If expected output matches with the actual output then we can ensure that out product is defect free. and if expected output not matches with the actual output then our product have some defects and we need to follow the procedure to fix the actual output.