Hi Friends,

I think this is a really good question, Not so difficult to answer but good one to discuss. My friend went for an interview in xansa, Noida, and this was the question asked by the interviewer, i really think on it, and found it better to discuss with all testers here.

Start replying.

__________________
--
Brijesh Jain

.......With Lots Of wishing on New Year to all of u......
hello dear friends
first of all
..............wishing u happy new year 2007 to all of u........
Really nice question.......
As per of my knowledge
if we r talking abt test data....
From ---> development team
1.it's given by the development team while they giving the s/w to teesting.
2.from the documents provided in reference of the testing for that project.

--->at part of testing team
1. The moment when test plans are prepared first stage they decided the uses cases wht could b these r.
2.then decide the possible test cases.
3. Now on the basis of all tht test data decided for testing. (coz it's deep testing so it's critical phase to deciding test data before goig for testing and it's decided during test plan decided by the testing team leads on the basis of docs getted for the deliverables & these docs could be
1.design document.
2.use case document.
3.unit+ intigration testing document by development team.
4.srs
friends if i m wrong
plz correct me i will b thank ful to all of u.
Regards
rajeev
(91-9818004180)

Test data may come from development team or the client company.

The data from development team is the test data used for white box testing, and that from client company will be real time data from their old data storage methods. Some clients may not agree to give real time data for data protection policies.

Test team may create their own test data not relying on the above mentioned sources. Creating large amounts of test data will be a tedious task, in such cases, a data generator like in the link below will be very handy.

Data Generator

__________________
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.

-sutnarcha-

For your kind information "Sutnarcha", test data from development team can also be used for black box testing.I have used that in my project.Still good answer, but i look forward for more satisfactory answer.

__________________
--
Brijesh Jain

In my previous post in this thread, I said

What I mean is it is the same data that the development team used for white box testing which can now be used by testing team for black box testing also. I didn’t mean to say that it is used for white box testing only.

I realize that my sentence (quoted above) is incomplete.

__________________
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.

-sutnarcha-

Waaw...That was a new piece of information for me....
In our company usually we testers used to create our own testdata...and test the application...Actually there is nothing called creation...We will test the application according to the context.....

Thanks for that Data Generator link Sutnarcha

Frm whr test data comes "test data comes from requirments or can say tht test data orizinates from the requirments" thnx & regards rajeev sharma

I really thanks sutnarcha for that data generator tool link.

Actually friends this is also a great question asked by interviewers that "which data generator tool you have used?".

sutnarcha; if you have link of more data generator tools, please share that with all, I sure it will really help all.

And friends make discussion cool.Contribute all in it.It's really a great topic for discussion.

__________________
--
Brijesh Jain

Guys i would like to add to the question in this thread.

I am mayank agarwal working in patni computer system as a software test engineer.
I would like to inform you about the test process and test data in particular.

the testing process goes like this:
1. KRT's(called Key Requirements Table) are written by a team in consultation with the client.
2. Test COnditions are written to satisfy the Requirements in KRT.
3. the KRT's are then grouped so that Test Case can be written for those KRT's.
4. Test Case is written for the KRT's grouped under one TestCase.
5. Test Case is reivewed by a separate team,defects are noitified to the test case designer, and also Test Data is identified by the team.
6. Test Data is populated in the system by the client side team according to the requirement given by review team.
7. Test Case is executed and defects if found are noitified.

Let we make discussion more interesting!

Now we will discus about Database testing in the same thread because they are inter-related and will be useful for the readers.

So what you see when you will do database testing?

Hey where you are my friends?
Please disscuss the topic friends.It's really cool.

__________________
--
Brijesh Jain

I think, we will do database testing:

01. if there is no user interface for the application
02. Also, in case of database migration (verify indices, field names, etc)

What are the characteristics of good Test Data?
What should be the approach towards choosing test data for (a) Manual testing (b)Automated Testing?

I dont think there is something called Good test data because if the Test data provided suits ur test & passes then it shud be the right test data or else u consider it as a bad test data

The question is not of what data is good? The question asks about the characteristics i.e. whenever we are chhosing a data set, what characteritics we should look for?
AND... Well we are not choosing test data just to pass the tests. Not a good testing practice u see.

See then it depends on the functionality u test yaa..

What are the characteristics of good Test Data?
What should be the approach towards choosing test data for
(a) Manual testing
(b)Automated Testing

dsharma, Do you mean data set here as data format ,it might be on any constraints like Integer,Character,Alpha numberic or Date.

I don't clearly understand whats mean by data set here?

Please clarify.

Regards,
Sridevichitthu

The Importance of Data In Functional Testing

• Plan the data for maintenance and flexibility
• Know your data, and make its structure and content transparent
• Use the data to improve understanding throughout testing and the business

A system is programmed by its data. Functional testing can suffer if data is poor. This presentation gives an understanding of the ways that data work fits into the overall test effort, and gives an overview of the ways that good data can be used to improve functional testing.

There are three kinds of test data;

1. Environmental data tells the system about its technical environment.
2. Setup data tells the system about the business rules.
3. Input data is information input by day-to-day system functions. Some input data is fixed and available at the start of the test. Some is consumable, and forms the test input.

The presentation deals with how to recognise these types and their common problems during pre-test, testing and go-live.

Data can be loaded into the system manually, or by tools. The presentation discusses the advantages and pitfalls of various methods and suggests partitioning strategies to allow reliability and flexibility in the same dataset. The frequency and timing of data loading is also discussed.

Data maintenance is a substantial task, often comparable in size with test script maintenance. The presentation discusses common problems and possible solutions. A key solution is that good data content can help reduce the workload of data maintenance.

Good data can allow testing to carry on in areas not covered by the initial scripts and requirements. Naming conventions can help data to be accurate, and can make test results easier to interpret. A good test data structure promotes a common understanding and helps avoid mistakes. Accurate and appropriate content reduces the number of test process errors.

Data can help the business focus when requirements are vague. User involvement in data descriptions allows early insight into possible problems. The presentation discusses the pitfalls and advantages of sourcing data from the business.

Hope this helps you to find the characteristis of Good Data.

Thanks and Regards,
Sridevichitthu

I am talking here about generalized characteristics of test data.
I can jot down few of the characteristics. A good test data set should be :
1) Realistic 2) Exhaustive 3) Reusable
But I need more characteristics...
And what about any special characteristics for a) Manual & b) Automated Testing?

A good test data is which one suits your requirement.It's most importantl.

Database testing test the integrity of database.

__________________
--
Brijesh Jain

I still haven't got the answer to the second part of my question "What should be the approach towards choosing test data for (a) Manual testing (b)Automated Testing?"