cindrela

 Profile Answers by cindrela Questions by cindrela

• Feb 27th, 2007

 

Examples of Domain are

1) Banking Domain
2) Insurance Domain
3) Finance Domain
4) Hotel Domain

These are the few examples
i am giving you.


I am not aware any thing as Domain Testing.
U can test the application on Banking,Insurance,Finance or Hotel Domain

hope this answer is satisfactory.
Regds
shailaja
sjsai70@yahoo.com

yagnanand

• Feb 27th, 2007

 

Shailaja has already told about the domains. In Domain testing the tester should have high competency level of domain knowledge. We can have either manual or automation testings.

kalyan M

• Feb 28th, 2007

 

The  important white box testing  method is domain testing. The goal is to check values taken by a variable, a condition, or an index, and to prove that they are outside the specified or valid range. It also contains checking that the program acepts only valid input...for this domain testing we should expert on that particular domain....

Sumit

• Mar 7th, 2007

 

Hi Sir,
May you give me more explanation on domain testing. I am not aware about it.
and may you tell me how we perform recovery testing

rajneeshbajwa

 Profile Answers by rajneeshbajwa 

• Mar 26th, 2007

 

kalyan if domain testinfg is white box testing then is there any difference between white box testing and domain testing?
Are they one and same thing?

preethi.gollamandala

 Profile Answers by preethi.gollamandala 

• Aug 11th, 2009

 

Domain: Its a specific area to which the project belongs
Domain testing is nothing but conducting testing on diffrent domains relarted to variuos projects,It varies based on projet area/Domain

Ex:
banking
Hospital
Insurance
E-retail etc

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Sep 9th, 2009

 

Domain: It is a field of study that defines a set of common requirements, terminology, and functionality for any software program constructed to solve a problem in that field.

Different Software Domains:
Banking
Finance
Insurance
E-Learning
Job Portal
Health Care
Shopping Portal etc..

Domain Testing:  Tester should aware and clear cut knowledge in the Domain makes him work effective in the differnt Domains.

prash_geek

 Profile Answers by prash_geek 

• Oct 8th, 2009

 

Domain Testing:  This testing is a generalization of equivalence partition testing with three-value boundaries. Domain means the set from which the values are selected. Hence in an EP testing we test for a specific range of values for which the system's or component's behavior is assumed to be same from compoment's specification.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 23rd, 2009

 

Domain refers to a body of knowledge in a particular field or industry.

Domain testing are testing activities that require knowledge of an industry's domain.  For example, testing a banking application is better served when the tester understands the banking industry.  In this case, the tester is said  to have domain knowledge of the application under test. 

mithr17

 Profile Answers by mithr17 

• Nov 2nd, 2011

 

@Kalayan_M : It would be great if you can explain terms by using examples. We all understand concepts well when examples are used. Clearly, you do not understand domain or how to test it. You just searched the term online, and copy/pasted someone else's content. Its infringement of copyrights when you do not give credit to the author and claim that as your answer. This may not be your intention but your actions speak louder than you intentions! Please refrain from such acts. Start giving credit to authors. This goes on to everyone.

If you look up for the meaning of "Domain" there are multiple meanings depending on the context. http://dictionary.reference.com/browse/domain

3 meanings will standout within the context of IT since we are talking about testing - (all taken from dictionary.com site)
(a) "Compare range the set of values of the independent variable of a function for which the functional value exists: the domain of sin x is all real numbers"

(b) "computing a group of computers, functioning and administered as a unit, that are identified by sharing the same domain name on the internet"

(c) "a field of action, thought, influence, etc.: the domain of science."

But, one one is more relevant to the question - domain & domain testing.

Everyone has rightly caught domain to be a field of action, thought, influence, etc.: the domain of science."

Domains can be thought of industries the application targets. Who will use this application? Or who does the application target?

eCommerce (online shopping)
Oil and gas
HR (human resources)
Education
Logistics
et all

Let me clarify: e-retail and e-learning are tools for online shopping (eComm) and online education respectively. They are not domains. Rather eCommerce and education are the domains. It would be more appropriate to use "eCommerce."

Domain can also be taken to be web domain. You can read more about it here:
http://en.wikipedia.org/wiki/Domain_name

Lets now move on to the more relevant meaning of domain.
(a) "Compare range the set of values of the independent variable of a function for which the functional value exists: the domain of sin x is all real numbers" (taken from dictionary.com site)

Domain testing is not purely white-box or black-box testing. It depends on which approach you apply. Meaning, it depends on "how" you intend to perform 'domain testing.' If you one of the white-box testing approaches like path analysis, mutation testing etc., is used to perform domain testing, then its white-box. If you apply functional testing methods like feature wise testing, boundary value testing, equivalence partitioning testing etc, are used, then its black-box.

But hey, developers (mostly) perform (unit testing) white-box testing. Path analysis, mutation testing etc., are white-box testing approaches.

Therefore, QA standpoint, domain testing is BLACK-box testing approach. We will visit this again at a later point.

So, what is domain testing?
Domain testing is a proven alternative to 'complete' testing and thus reduces the overall QA effort. It is a step-by-step approach aimed at "reducing an enormous test data set to few manageable test data subsets, and further reducing each of these sub-sets to few best representatives (best test cases)." (taken from Sowmya Padmanabhan's paper)

When we apply mathematical meaning of domain - "Compare range the set of values of the independent variable of a function for which the functional value exists." - the application can be thought of as one big function, and for each input value will yield an output value. So all input values will be in 'input domain' and all output values will reside in 'output domain.'

Thereby, the 'input domain' becomes the single most important piece of domain testing. QA needs to come up with input data set (domain) that can best test the application. No doubt, we will need to do some analysis on the output as well! The output in IT application will be screen displays (web pages, UI, etc), reports, interfaces etc, and output devices such as file systems.

While testing, we almost always encounter numeric data entry fields such as bank account #s, dates, salary, DOB, # children, emp Id, etc. The very purpose of 'testing' is to catch unwanted behavior (bugs) and deliver top quality product. Domain testing will be a great help when QA needs to test applications that involve numeric data entry.

The easiest way to "partition" test cases is by utilizing 'Equivalence class partitioning' testing and 'boundary value testing.' We partition input data to segregate invalid data from valid data, but input data domain will include both invalid and valid data.This way the input data domain can be formed to test and analyze output.

Example: QA is asked to test a date field that does not have calendar attached to it. Meaning, calendar does not automatically pop-up, rather user needs to manually enter date in MM-DD-YYYY format. As we know, MM will accept values 1 to 12 (12 months in an year) and DD will accept 1 - 31 (max of 31 days in a month). Let's say year is limited to values between 2001 and 2012.

So the input data set for month - MM:
Invalid data - <1 (...,-1,0) and >12 (13, 14..)
Valid data - 1 to 12 including 1 and 12

1<= X <= 12 (mathematical equation form)

Input domain for DD:
Invalid data: <1 (..,-1,0) and >31 (32,33,..)
Valid data : 1 - 31 including 1 and 31

1<=Y<=31 (mathematical equation form)

Input domain for YYYY:
Invalid data: <1 (...,1999,2000) and >2012 (2013, 2014..)
Valid data: 2001 - 2012 including 2001 and 2012

2001 <=Z<=2012 (mathematical equation)

Notice I have used only 2 number. that's because I applied boundary value to the boundary min and max limits.

QA tested it and found some critical bugs, all closed well and good. But, the dev must have coded it differently. Dev may have coded 1-4 months and again 5-12 months because company's fiscal year end is month 4.

Therefore, while performing domain testing, grey-box testing approach is best suited instead of just using white/black! Some knowledge of how code was written for numeric fields will greatly help QA in covering "black (no knowledge of internal code)" and "white (some knowledge of code)" based scenarios with slight alteration in input domain.

For more on domain testing, you can read :
http://www.testingeducation.org/a/DTD&C.pdf
http://testingeducation.org/a/tdtsr.pdf

Thanks for reading through the article!