One method is With the testcase itself include test data.
If bulk amount of data exist to test in various conditions,
Keep the fields in the page as columns in excel sheet and
give the data with various combinations.
Any other information please inform me
Aparna, iam rafi from CTS can you put it clearly, you mean
based on the pre-requesite we have to map the test data
thatis what you mean or ??
Rafi - Programmer analyst
CTS
hi rafi ... this is not the right way.. if you now the
answer please give the right way... if you dont no dont
send those stupid posts...if you are a genious give the
proper answer dont disapoint....
Preparing proper test data is a core part of “project test
environment setup”. Tester cannot pass the bug
responsibility saying that complete data was not available
for testing. Tester should create his/her own test data
additional to the existing standard production data. Your
test data set should be ideal in terms of cost and time.
Design our test data considering following categories:
Test data set examples:
1) No data: Run your test cases on blank or default data.
See if proper error messages are generated.
2) Valid data set: Create it to check if application is
functioning as per requirements and valid input data is
properly saved in database or files.
3) Invalid data set: Prepare invalid data set to check
application behavior for negative values, alphanumeric
string inputs.
4) Illegal data format: Make one data set of illegal data
format. System should not accept data in invalid or illegal
format. Also check proper error messages are generated.
5) Boundary Condition data set: Data set containing out of
range data. Identify application boundary cases and prepare
data set that will cover lower as well as upper boundary
conditions.
6) Data set for performance, load and stress testing: This
data set should be large in volume.
This way creating separate data sets for each test
condition will ensure complete test coverage.
Preparing Test data is very important before we execute the
test cases. Test data must be created for each and every
test cases. Test data can be prepared with the knowledge of
Boundary Value Analysis and equivalence class partition.
Ex: The test data for customer name field with the
condition such as 5 to 15 chars and no special symbols
would be
Boundary Value Analysis:
min i.e 5 chars: arthu result: system should accept
min-1 ie 4 chars: qwer, result: should prompt error message.
max ie 15 chars: qwertyuioplkjhg : system should accept.
max+1 ie 16 chars: qwedsafgtrfdsert: system should prompt
error message.
Equivalence class partition:
include all the special symbols or numbers in the middle.:
system should prompt error message.
Friends plzz let me know if i am wrong or u get more
generous answer. Thank You
Understanding the business logic is often very important.
also, it would be helful if customer provided data is
available, which will help in getting a deeper kowledge
about the amount and type of actual data tat is expected to
go into the DB.
Suppose ,if we are taking 1 field for which we are going to
Prepare Test data.We are going to consider the Boundary
Values as well as ECP in preparation of Test Data
Praveen Kumar.D
Prapan SOlutions India PVT LTD
As a tester how much server knowledge is enough to know. I
worked in Tomcat 5 and Jboss 4.0.3 server but I didn't have
any knowledge on that please help me to know more about
this? i had lot of questions in this. What architecture,
what configuration, draw how it works..but not able to
manage. please help me.
This is a common login screen example with all well known
fields like username, password, etc.
How could you test this in Unit Testing Phase, Integration
Testing Phase and System Testing Phase??