Object Oriented Software Engineering   View all facts   Glossary   Help

subject > problem > defect > timing and co-ordination defect > critical race

critical race (race condition)
subject			fact

critical race	can be detected by glass-box testing since you can actually study the progress and states of the various threads
	can be detected by inspection
	has definition A defect in which one thread or process can sometimes experience a failure because another thread or process interferes with the 'normal' sequence of events
	has black-box testing strategy Vary the time consumption of different threads by giving them differing amounts of input, or running them on hardware that varies in speed Run a large number of threads concurrently Deliberately deny resources to one or more threads (e.g. temporarily cut a network connection, or make a file unreadable)
	is hard to detect with black box testing alone since you often don't know the extent of the concurrency going on inside the system, and can not always manipulate the various threads to cause race conditions
	is a subtopic of 10.5 - Defects in Timing and Co-Ordination: Deadlock, Livelocks and Critical Races
	is a kind of timing and co-ordination defect
	is a synonym of race condition
timing and co-ordination defect	occur when several threads or processes interact in inappropriate ways
	only occurs in a situation involving some form of concurrency
defect	has example the absence of code to handle an exception
problem	has solution which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution
	should be written as a simple problem statement in one or two sentences