Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Hi Pals
I have found that Sridevichittu's Thread more informative.
Here the thread was posted as "Where the test data comes from".
But the Threads were posted for Good Test Data.
I would like to post the answer to this thread as per my knowledge n experience as
For the legacy application( application which are developed already in other technologies) which have to be developed on other technology then the data would be available for the test team, then the test team prepare test data documents in their own interpretable format.
Where as for the newly developed applications
test data will be provided by the developed team.
I was involved in testing the application, which is related to life science
for which test data was provided but that is not in format(mixed test data).
Here format in the sence for instance
Advanced search in which v would be providing the data i.e search terms in different fields as journal name,author,content type and so on.
So the test data will be different for certain journal name.
Hope this thread is understandable.
Any corrections are acceptable
Thanks
What are the characteristics of good Test Data?
What should be the approach towards choosing test data for
(a) Manual testing
(b)Automated Testing
A good test data is that which is as close to as real data for the application.
For both (Manual testing, Automated Testing) we can use a data generator tool.
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
A good test data is the one that uncovers more bugs/defects.
It is as simple as that. But to put it in points, we can say, a good test data is
-a perfect combination of values to meet or set the test scenario as initial state for applying the test case.
-a good variation in values to apply the test case effectively and completely.
-values that try to break the functionality for the purpose of uncovering defects.
-both negative and positive values in and around the boundaries.
-something that is close to the real time data like ‘jainbrijesh’ said.
Even if these characteristics are not met, if any data uncovers more bugs/defects in a software, then it can be graded as a good test data.
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.
-sutnarcha-
Hi all,
My opinion, test data comes from:
1. Project requirement
2. Experience
3. Data causing bugs of old version
4. Data causing bugs of bug data
5. Standard which the application is belongs to, ex: application for blinds
6. Data causing bugs of the same kind of project.
Tks for letting me know if I'm wrong.
Hi All,
1) A database dump of the real data can be asked for from the client. If there is any company policy which restricts them from giving the database dump then it will be point two mentioned below.
2) Testers can prepare test data after getting sufficient input from the client. But as mentioned by many of us the data creation for a huge application is going to be a tough job.
3) The test data can also prepared in consulation with the development team.
Hi all,
Test data - entirely depends on the sort of application being tested. Based on the testing techniques being applied on the application the test data varies.
we either go to generate the test data based on documents like BRS/URS (applying the methodologies like BVA & ECP) , or take data from the production database (with changes where ever necessary)
Hi all
What is meant by Test Data?
What are the components involved in test data?
who will prepare test data?
From where test data comes?
can anybody plz explain about this with an example?
thanx
Bharathi
These questions are answered quite a few times in Geek. Please search for them
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.
-sutnarcha-
who will prepare the testdata?
a) Tester
b) developer
c) client
d) Test Manager
Last edited by jainbrijesh; 06-14-2007 at 06:17 AM.