How will be the testcases for product testing . Provide an example of test plan template

  • Interview Candidate
  • 23
  • 8675

  
Showing Answers 1 - 23 of 23 Answers

vijay

  • Aug 2nd, 2005
 

Test plan is same there no seperate test plan for product testing

  Was this answer useful?  Yes

suma

  • Aug 5th, 2005
 

In the Test Plan for the Product testing, new components if any added or the enhancements made to the products will be mentioned.

  Was this answer useful?  Yes

Raj

  • Aug 11th, 2005
 

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 Stratergy section you need to clearlly mention what are the things that your going to test. So this may vary from product to product. 

  Was this answer useful?  Yes

Beena Kadam

  • Aug 29th, 2005
 

For product testing, the test plan includes more rigourous testing since most of these products are off the self CD buys or net downloads. 
 
Some of the common parameters in Testing must include 
------------------------------------------------------- 
1) Testing on Different Operating Systems 
2) Installations done from CD ROM Drives with different machine configurations  
3) Installations done from CD ROM Drives with different machine configurations with different versions of Browsers and Software Service Packs 
4) LICENSE KEY functionality 
5) Eval Version checks and Full Version checks with reference to eval keys that would need to be processed.

Vikram

  • Sep 26th, 2005
 

In Product base testing,

We need to collect all the requirement such as test setup,Test envir*,Phisical requirement and what we have to achive by doing testing.

these kind of documnet is called as Test Discription Document.

  Was this answer useful?  Yes

Beena Kadam

  • Sep 26th, 2005
 

Product Testing should consider the following

1)       Operating Systems :-What the SRS refers to with respect to the operating systems on which the Product should work

2)       Load Testing - What is the expected Database load that can be carried with optimum efficiency with reference to SRS

3)       Performance Testing  :-Form load time with minimum and maximum databases loads of varying strengths

4)       Machine Configurations :-Different machine configurations on which the product should be designed for with reference to the SRS

5)       Exe installations from CD \ Floppy \ Pen Drives \ Internet lines or any other method as asked for in SRS

6)       License Checks ? Number of licenses applied for or allowed as per SRS

7)       Multi User checks ? Depending on the SRS check for mutli user \ single user testing

Client Server Applications :- Check how many user ?Clients? can be created and run successfully

  Was this answer useful?  Yes

Beena Kadam

  • Sep 26th, 2005
 

Product Testing should consider the following

1)       Operating Systems :-What the SRS refers to with respect to the operating systems on which the Product should work

2)       Load Testing - What is the expected Database load that can be carried with optimum efficiency with reference to SRS

3)       Performance Testing  :-Form load time with minimum and maximum databases loads of varying strengths

4)       Machine Configurations :-Different machine configurations on which the product should be designed for with reference to the SRS

5)       Exe installations from CD \ Floppy \ Pen Drives \ Internet lines or any other method as asked for in SRS

6)       License Checks ? Number of licenses applied for or allowed as per SRS

7)       Multi User checks ? Depending on the SRS check for mutli user \ single user testing

Client Server Applications :- Check how many user ?Clients? can be created and run successfully

  Was this answer useful?  Yes

Laxman

  • Oct 5th, 2005
 

There will not be much of difference between a product testing and project testing. In Product testing we basically test for Major Enhancements, Minor Enhancements, Defects logged. There will be Releases in Versions, Service Packs, RollUps. We basically test for all these releases.

  Was this answer useful?  Yes

Sujatars

  • Feb 27th, 2007
 

In Project testing the end user(h/w & s/w)  requirements are know ,a particular program will be used by a spcific group of people with specfic test requirement.

But for Product testing u need to port the product on different OS, different platforms,test for Interoperability.

  Was this answer useful?  Yes

korukondaqa

  • Apr 29th, 2007
 

There is no rigid rule for the Test Plans. This is completely depends on the Project/Product/Company/ etc. So many factors impact this.

Generally, While defining any of the process for all types, the broad category would be Product and Project.There may be some project life cycle similar to basic product life cycle. The main idea of this categorization is, Product is never ending process. For this the basic test plan is same but there would be more releases or Appendix for this test plan for all the Enhancements/New features that are coming in to the product. 

Coming to the Test cases, Generally They follow Incremental test case build process using their company standards/methodology.


  Was this answer useful?  Yes

AaAa

  • Oct 4th, 2007
 

For product testing test cases will be in intergration format...

  Was this answer useful?  Yes

ntnath

  • Oct 28th, 2007
 

Project Testing and Product testing are different as product testing is evaluated over a period of time whereas project testing is testing the complete version.  Test plan should be generic and any new changes must be incorpated as and when needed.  Product Test plan almost covers all types of testing from functionality to system and security, performance and load testing.  It may also include logo testing for the approval from certain vendors.

srinivasulub1981

  • May 7th, 2009
 

Hi

   I feel writting test cases for a project is little bit different than product , we have followed in the below process.

1. First raw (Common functionalities) test cases will prepared and stored at VSS

2. Next for new client, we take that raw test cases and modified as per the new company requirements

3. So will maintain the cases per company wise

4. If at all new changes came we will update accordingly

5. Make sure that added new changes will not be effect the existing clients



Thanks,
Srinivas

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions