What do u mean by TestData.How many Types of TestData are there.
First - put a meaningful name to this topic. Almost EVERYTHING in these forums is a "query." You can go back and edit it.
Second, please do not use texting. We consider it immature and unprofessional here. The word is "you" not "u."
Third, before we even begin to respond to such an extremely basic question (the likes of which seem even below interview level), please try a Google search for "test data" - including the quotes. You could even try entering "what is test data" (note that "test data" consists of two words, not one).
I didn't know about 'define'. Thanks [img]/images/graemlins/smile.gif[/img]
Test data is the data which helps us to execute the test cases with various input details.
Environmental data tells the system about its technical environment. It includes communications
addresses, directory trees and paths and environmental variables. The current date and time can be seen as environmental data.
Setup data tells the system about the business rules. It might include a cross reference between country and delivery cost or method, or methods of debt collection from different kinds of customers.
Typically, setup data causes different functionality to apply to otherwise similar data. With an effective approach to setup data, business can offer new intangible products without developing new functionality - as can be seen in the mobile phone industry, where new billing products are supported and indeed created by additions to the setup data.
Input data is the information input by day-to-day system functions. Accounts, products, orders, actions, documents can all be input data. For the purposes of testing, it is useful to split the categorization once more:
FIXED INPUT DATA
Fixed input data is available before the start of the test, and can be seen as part of the test
CONSUMABLE INPUT DATA
Consumable input data forms the test input
It can also be helpful to qualify data after the system has started to use it;
Transitional data is data that exists only within the program, during processing of input data.
Transitional data is not seen outside the system (arguably, test handles and instrumentation make it output data), but its state can be inferred from actions that the system has taken. Typically held in internal system variables, it is temporary and is lost at the end of processing.
Output data is all the data that a system outputs as a result of processing input data and events. It
generally has a correspondence with the input data (cf. Jackson's Structured Programming
methodology), and includes not only files, transmissions, reports and database updates, but can also include test measurements. A subset of the output data is generally compared with the expected results at the end of test execution. As such, it does not directly influence the quality of the tests.
This is ripped off, without citation, from a copyright source: http://www.workroom-productions.com/...%20Fn%20Te.pdf