Test Development

Question

0.00/5 (No votes)

See more:

Hi, I have the task of to take the tests of our software

I have not already do that before so, where should i start exactly?

Is important to me creating a structure which is also useful.

Does anyone have experience with it, perhaps how to start something?

I am grateful for any information ..

Posted 25-Jan-11 23:59pm

DevJunk

Updated 26-Jan-11 2:24am

#realJSOP

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ryan Zahra · Accepted Answer · 2011-01-26T00:09:00

Solution 1

Start by knowing exactly what the code should do and then try different test cases.
You should also consider using unit testing. This is an excellent starting point
http://www.dreamincode.net/forums/topic/108976-c%23-unit-testing-basics/

Posted 26-Jan-11 0:09am

Ryan Zahra

Ger Hayden · Accepted Answer · 2011-01-26T02:21:00

First of all, try ignore the code - if you are familiar with it.
Get copies of the business requirements and functional specification.
Have a general test that does very little but at least proves the installation is successfull.
This will give your release / packaging people a heads up if there are deployment issues.
Test that each requirement works.
Test that each function works.
Try to break things - e.g. sticking alphas in number fields.
Test date validation e.g. February 29/30, June 31.
Do volume testing - does performace fall off as the transaction count rises.
Simultests - two users attempting the same task at the same time.
Fail over testing. What happens to complex transactions when the computer / power fails mid way?