What is Test Plan?

test-plan

If you have any quarries/feed back send me on - knowthetesting@gmail.com
Thank you
Ram

Product testing Interview questions

Q. How will be the test cases for product testing? Provide an example of test plan template?

A. The concept of Product Testing varies from company to company. When you talk of a Product, that product can be a ERP software, Banking application product, Billing Product.

So when your writing test cases for the product you need to keep in mind one main thing that is ''Check for Business functionality'. Your test case should cover the above aspect with all the other like field validation.

For writing Test Plan, Under the Approach and Strategy section you need to clearly mention what are the things that your going to test. So this may vary from product to product.

Q. What are the advantages of working (as a tester) for a product based company and a service based company?

A. In product based company, the tester will come out with creative idea about the products. he think like a client when changes were being made. Products are basically should have less work and more out put to client. Where as for applications, once it is done it will be implemented and maintenance work will be there once in a year as per the company policy

Q. How product based testing differs from Project based testing. Give me a suitable example

A. There is no much difference between product and project. product is some thing that first it will be developed, tested and sale it to clients, where as project is taking the requirement, develop, test and then hand over to client

1) product will take lot of changes according to different clients and the nature of business. Where as application take only few changes until client satisfies.

2) Single product can be sold to multiple clients, where as applications are as per the client requirement

3) product--demo--client approve--sale

application--client requirement--develop--approve

Q. What is meant by Test Plan? What will be included in it? Give a sample Test Plan for a Login Screen

A. I think there is a lot of confusion between a test plan and test case.

Test Plan: Test Plan is a document consisting of scope, objective, approach, schedule of the testing activities for the specific project. It mainly consists of who to test? when to test?, why to test?, where to test?

IEEE 829-1983 standard test plan consists of different fields like, Test plan ID, Introduction, Test Items, Features to be tested, Features not to be tested, Testing tasks, Schedules, Training and Environmental needs, Test Approach, Deliverables, Item pass/fail criteria, test suspension criteria, human resources.

For login screen, test plan can be created. But it is not important to create test plan for login screen alone. A test plan will be created for the whole project. For Login screen, test case's can be created and executed to find defects.

Test case is a document consists of Serial Number, Steps Description, Expected, Actual, Test Data, etc. A test case is derived from SRS, FDS, Use Case's etc. For login screen, a user interface test case can be created to check the spelling and location of user name, password, and text boxes and for buttons ok and cancel and any remaining items on that screen.

Input domain test cases can be created for User Name and Password. Techniques like equivalence partitioning and boundary value analysis is used to create test data. Test data is divided into valid boundaries and invalid boundaries. For all valid boundaries positive tests and for each invalid boundary negative test can be created

Q. What is the difference between testing a product and testing any web -based application?

A. if product is a client based one then there is difference between this both but if the product is web based then no difference in my view product is build by company and kept for sale as to be sold by customers who needs them and product will be customized as per required changes (if needed) and sold to customer. in sense ur question is some what confusing as it should product testing Vs project testing otherwise web testing Vs client server testing

Q. Difference between Web based testing and Client server testing

A. Web Based Application: here you are going to check the application which is going to be launched on the internet or intranet. Means it is in the form of web pages.

Client Server application: Basically the applications used in LAN in which a client and a server is present. In this a .exe file of the application stored at the server is called from the client and accessed and all the database is stored in the application.

Q. How to do SOAP Testing manually?

A. Easiest way....ask developers to provide a client tough way.....learn HTTP n SOAP a little write client programs to call the server..U can use perl/python

OR

SOAP is simple object access protocol, uses for the data transmission between two applications, its better to understand the structure of SOAP, and test it by wrong format, and check whether it can carry all type of datas into it. Give wrong XML format into it and send it, send a non-authorized name space into it, but when you want to test the capability or maximum output from the SOAP you need to test the how big request message it can carry by creating a big SOAP.

Q. How Waterfall model can be used in developing a product?

A. Usually products are first developed and then it is sold to customers. so even u follow the water fall method, at last u have to change some features according to their demand requirement. Client may ask for design change after coding and testing, so difficult to maintain the water fall method.

Q. How will be the test cases for product testing? Provide an example of test plan template

A. totally agrees wtih mr.Amte. As u don’t have any particular requirement. So u have to discuss with team and write test cases. But personally u need to note the fundamental features and restrictions of different features and then start write test case. Just like Name options: no blank space, only characters

phone number: no blank numbers, only numerical, limited to 10 numerical

If you have any quarries/feed back send me on - rampeddireddy2006@gmail.com, ram@examsinfo.in.

Thank you

Ram

Software Testing Life Cycle

Software testing life cycle identifies what test activities to carry out and when (what is the best time) to accomplish those test activities. Even though testing differs between organizations, there is a testing life cycle.

Software Testing Life Cycle consists of six (generic) phases:

• Test Planning,
• Test Analysis,
• Test Design,
• Construction and verification,
• Testing Cycles,
• Final Testing and Implementation and
• Post Implementation.

Software testing has its own life cycle that intersects with every stage of the SDLC. The basic requirements in software testing life cycle is to control/deal with software testing – Manual, Automated and Performance.

Test Planning

This is the phase where Project Manager has to decide what things need to be tested, do I have the appropriate budget etc. Naturally proper planning at this stage would greatly reduce the risk of low quality software. This planning will be an ongoing process with no end point.

Activities at this stage would include preparation of high level test plan-(according to IEEE test plan template The Software Test Plan (STP) is designed to prescribe the scope, approach, resources, and schedule of all testing activities. The plan must identify the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan.). Almost all of the activities done during this stage are included in this software test plan and revolve around a test plan.

Test Analysis

Once test plan is made and decided upon, next step is to delve little more into the project and decide what types of testing should be carried out at different stages of SDLC, do we need or plan to automate, if yes then when the appropriate time to automate is, what type of specific documentation I need for testing.

Proper and regular meetings should be held between testing teams, project managers, development teams, Business Analysts to check the progress of things which will give a fair idea of the movement of the project and ensure the completeness of the test plan created in the planning phase, which will further help in enhancing the right testing strategy created earlier. We will start creating test case formats and test cases itself. In this stage we need to develop Functional validation matrix based on Business Requirements to ensure that all system requirements are covered by one or more test cases, identify which test cases to automate, begin review of documentation, i.e. Functional Design, Business Requirements, Product Specifications, Product Externals etc. We also have to define areas for Stress and Performance testing.

Test Design

Test plans and cases which were developed in the analysis phase are revised. Functional validation matrix is also revised and finalized. In this stage risk assessment criteria is developed. If you have thought of automation then you have to select which test cases to automate and begin writing scripts for them. Test data is prepared. Standards for unit testing and pass / fail criteria are defined here. Schedule for testing is revised (if necessary) & finalized and test environment is prepared.

Construction and verification

In this phase we have to complete all the test plans, test cases, complete the scripting of the automated test cases, Stress and Performance testing plans needs to be completed. We have to support the development team in their unit testing phase. And obviously bug reporting would be done as when the bugs are found. Integration tests are performed and errors (if any) are reported.

Testing Cycles

In this phase we have to complete testing cycles until test cases are executed without errors or a predefined condition is reached. Run test cases --> Report Bugs --> revise test cases (if needed) --> add new test cases (if needed) --> bug fixing --> retesting (test cycle 2, test cycle 3….).

Final Testing and Implementation

In this we have to execute remaining stress and performance test cases, documentation for testing is completed / updated, provide and complete different matrices for testing. Acceptance, load and recovery testing will also be conducted and the application needs to be verified under production conditions.

Post Implementation

In this phase, the testing process is evaluated and lessons learnt from that testing process are documented. Line of attack to prevent similar problems in future projects is identified. Create plans to improve the processes. The recording of new errors and enhancements is an ongoing process. Cleaning up of test environment is done and test machines are restored to base lines in this stage.

Software Testing Life Cycle
Phase	Activities	Outcome
Planning	Create high level test plan	Test plan, Refined Specification
Analysis	Create detailed test plan, Functional Validation Matrix, test cases	Revised Test Plan, Functional validation matrix, test cases
Design	test cases are revised; select which test cases to automate	revised test cases, test data sets, sets, risk assessment sheet
Construction	scripting of test cases to automate,	test procedures/Scripts, Drivers, test results, Bugreports.
Testing cycles	complete testing cycles	Test results, Bug Reports
Final testing	execute remaining stress and performance tests, complete documentation	Test results and different metrics on test efforts
Post implementation	Evaluate testing processes	Plan for improvement of testing process