1 / 37

Issues in Testing OO Programs (7.1, 2.2.2, 2.4.2)

Issues in Testing OO Programs (7.1, 2.2.2, 2.4.2). Course Software Testing & Verification 2013/14 Wishnu Prasetya. Plan. The goal is to discuss how to test OO programs; to that end we also need some concepts from: Data flow perspective to testing Integration testing. Basic idea.

tess
Download Presentation

Issues in Testing OO Programs (7.1, 2.2.2, 2.4.2)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Issues in Testing OO Programs(7.1, 2.2.2, 2.4.2) Course Software Testing & Verification 2013/14 WishnuPrasetya

  2. Plan • The goal is to discuss how to test OO programs; to that end we also need some concepts from: • Data flow perspective to testing • Integration testing

  3. Basic idea • The two paths of P above will carry the same value of x “defined” at the beginning to the return statement. • Do we need to test both paths? Purely with respect to the influence on x probably not. • Control flow graph cannot make the distinction between which paths are equivalent with respect to their effect on a selected set of variables. P(x,y) { if (y<x) y = x+1 ; return x*y }

  4. Data-flow based approach(sec. 2.2.2) n0 def (n0) = { x,y } • Data flow graph : CFG, where the nodes and edges are decorated with information about the variables used and defined by each node/edge. • In my examples I avoid decorating on the edges. • Some subtlety on the granularity of the nodes/edges  later. P1(x,y) { if (y<x) y = x+1 ; return x*y } use(n1) = {x,y} n1 (then) use{n2) = {x} def(n2) = {y} n2 n3 use(n3) = {x,y}

  5. Terminologies • Def/use graph: see above. In general, def/use labels are allowed on the edges as well. • A path p = [i,...,k] is def-clear wrt v iff v  def(j) and v  def(e)for all nodes j and edges e in pbetweeni and k. • It (def-clear) is a du-path wrt v iff vdef(i) and vuse(k), and furthermore it is a simple path. use = {x,y} def ={x} use = {y} def = {y} du-paths wrt x: 13, 134, 135 12, 1234, 1235, 45 Not du-path wrt x: 1345 (not clear) n4 n2 use = {x,y} def =  n1 n3 n5 use = {x,y} def = { x,y } use = {x,y} def = 

  6. Block’s granularity • When a node both defines and uses the same variable x, we will assume that it uses x first, then assigns to it, as in x = ... x ... • If this assumption would be broken  split the node. Else this will conflict the intention of your definition of du-path. • Check 2.3.2 on how to map a source code to a def/use graph. x = x+1 y = y+1 ; x = 0 x = x+1 x = x+y use(n1) = {} def (n1) = { x} n1 use(n) = {x,y} def (n) = { x,y } use(n) = {x,y} def (n) = { x } n n use(n2) = {x} def (n2) = { x} n2

  7. Data-flow based coverage(Rapps-Weyuker 1985, Frankl-Weyuker 1988) • Def-path setdu(i,v): the set of all du-paths wrt v, that starts at i. • Def-pair set du(i,j,v): the set of all du-paths wrt v, that starts at i, and ends at j. • Same concept of touring. • (C 2.9, All Defs Covrg, ADC) For each def-path set S = du(i,v), TR includes at least one member of S. use = {x} def ={x} use = {x} def = use ={x} def =  n1 n3 n4 n2 use = {x} def = { x,y }

  8. Data-flow based coverage • (C 2.10, All Uses Covrg, AUC) For each def-pair set S = du(i,j,v), TR includes at least one member of S. • (C2.11, All du-paths Covrg, ADUPC) For each def-pair set S = du(i,j,v), TR includes all members of S. use = {x} def ={x} use = {x} def = ADC TR: 12, 234 AUC TR: 12 23 , 232, 234 ADUC TR: 12 23 , 232, 234, 24 use ={x} def =  n1 n3 n4 n2 use = {x} def = { x,y }

  9. Overview of subsumption relations complete path covrg • PPC  ADUPC, because every simple path is a subpath of some prime path. • AUC  EC ... the argument is a bit contrived. AnO assume: • every use (of v) is preceded by a def. • every def reaches at least one use. • arrows are labelled; arrows that leave the node imust use at least one var, and they all must use the same set of vars. prime path covrg ADUPC edge-pair covrg AUC edge covrg ADC node covrg

  10. Summary • Data-flow based testing ia an alternative to prime-path testing, if the latter becomes too expensive. • Also a useful concept for integration testing and OO testing.

  11. Integration Test • To test if a component P that is a composition of smaller “components” works correctly. • When have we tested this enough? • Problem : the combined CFG is complex, leads to many paths to cover. • Using the “connections” between P and its components to define coverage.

  12. AO’s discussion on Integration Test • “Hidden” in Section 2.4 about using design elements (e.g. your UML models) as your coverage criterion. AO see this as a trend, but 2.4.1 is a bit vague. But do say: “testing software based on design elements is usually associated with integration testing”. • 2.4.2 is actually more about integration testing rather than design-element-based testing.

  13. Data flow approach to Integration Test (2.4.2) A • Imagine method f from module A calls method/API g from module B. • Idea 1: construct the combined CFG of both, then use prime path coverage criteria. Blow up... some paths are perhaps “equivalent” with respect to the interaction between f and g. • Idea 2: focus only on the flow of the “coupling data” around the call point. f (a) { ... g(e) ... } B g(x) { ... }

  14. Coupling (1) g(x) • caller, callee, actual parameters, formal parameters • parameter coupling, shared variable coupling, external device coupling • More general concept: coupling variable  a ‘variable’ defined in one ‘unit’, and used in the other. (1) a = ... ;b = ... (2) x<=a (4) return ... (2) a>b (3) a = ... (3) x==a (4) b = g(b) (5) return ...

  15. Coupling du-path(Jin-Offutt, 1998) (1) g(x) • (Def 2.40) Last-def of v : set of nodes defining v, from which there is a def-clear path (wrt v) through the call-site, to a use in the other unit. • Can be at the caller or callee! Example: f1, f3, g4, g5. • (Def 2.41) First-use (of v)E.g.: g2, f4 • Coupling du-path of v is a path from v’s last-def to its first-use. (1) a = ... ;b = ... (2) x<=a (4) return ... (2) a>b (3) a = ... (3) x==a (4) b = g(b) (5) return ...

  16. Now you have your Integration Test-Requirement Coupling vars: a, b, g.return Coupling du-paths : a: [f1,f2,g1,g2] [f3,f4,g1,g2]b: [f1,f2,g1,g2] [f1,f2,f3,g1,g2]g.return: [g4,f4] [g5,f4] • ADC All Coupling Def Cov. : for every last-def d of each coupling var v, TR includes one coupling du-path starting from d. • AUC  All Coupling Use Cov. : for every last-def d and first-use u of v, TR includes one couple du-path from d to u. (1) a = ... ;b = ... (1) g(x) (2) a>b (2) x<=a (4) return ... (3) a = ... (3) x==a (4) b = g(b) (5) return ...

  17. First use at the callee .. • When you just pass a variable as in g(b), it makes sense to define g’s first use to be the first time g uses the parameter (location g.3 in the previous example). • But when you pass a complex expression like g(a+b)  what are g’s first uses of a and b?  in this case it make sense to define g’s first uses (of a and b) to be at the call location itself.

  18. Sources of problems in OO programs(in addition to the traditional ones) • A function behaves “cleanly”; a procedure does not. An OO program: even worse: • non-functional interaction through instance variables and static variables • interaction through inheritance • dynamic binding • access control (priv, pub, default, protected, ...)

  19. Anomalies • Simply mean non-standard situations. Not necessarily errors, but they tend to be error prone. AO list 9 anomalies related to inheritance and dynamic binding: • Inconsistent Type Use (ITU) • State definition anomaly (SDA) , ... 7 more • AO also implicitly discuss two more: deep yoyo and data-flow anomaly.

  20. Inconsistent Type Use (ITU) anomaly List +insertElemAt(i:int) +remElemAt(i:int) Stack +push(x) +pop() (Not the structure is anomalous, but its use might be) Obviously it is ok to use a Stack as a Stack. However, if the programmer sometimes uses a Stack also as a List  this is error prone. Calling insertElemAt or remElemAt on a Stack which you intend to use as a stack is obviously dangerous.

  21. State Definition Anomaly (SDA) UnitItem scale = 1 price() { return 1/scale } • A subclass A1’s state is partially made of its superclass A’s states. Through extension or overriding, the A1 may directly manipulate its super-state part rather than via A’s methods; this may break A’s assumptions on that part. • It would be useful if a class invariant for A is defined. MultiItem quantity MultiItem() { quantity=1 ; setScale(2) } setQuantity(q) (error prone) ScalableItem setScale(s) { scale = s } (OK...)

  22. State definition inconsistency due to state variable hiding (SDIH) • A subclass A1 of A shadows an instance variable x of A, while some methods m of A uses x. So, when m is called from A1, it will use the super-x, rather than the new x. Item price tax netPrice() { return price * (1 + tax) } setPrice(p) { price = p } OnSaleItem price sale(p) { price = 0.8 p }

  23. State Visibility Anomaly (SVA) • A • x • + incr() B C + incr() C’s needs to implements its own incr. However it can’t get to x, because it is private to A. The only way to do it is through A’s incr. This can be done simply by calling super.incr(). So far it is ok. Now imagine someone else changes B by overriding incr. This suddenly changes the behavior of C; as it now calls B’s incr instead.

  24. Anomalous Construction Behavior 1 (ACB1) • A1 is a subclass of A. A’s constructor calls r(). A1 overrides this r. If A1’s constructor calls super, it will then calls the new r instead (notice the Yoyo there). In the above example, it breaks because reset() would use an uninitialized baseprice (can btw be recognized with a Yoyo+dataflow graph, as shown later). Item price tax = 0 Item() { reset() } reset() { price = 1 } ExpensiveItem baseprice ExpensiveItem() { super() ; baseprice=10 } reset() { price = baseprice }

  25. Need concept: call graph • A graph describing which program “units” call which. . • However, in OO, due to overriding, the call graph of the same method in the subclass may be different. While this is not surprising, we can create a “yoyo” that makes things error prone. f We’ll define f g means f contains a call to g in its body (note that it does not mean that in the runtime f will actually call g; it may depend on its parameters) The two branches from f in the example says nothing about the order in which the children will be called by f. g h

  26. The call graph of d() in ABCyoyo graph, Alexander-Offut 2000 A +d () { g() } +g () { h() } +h () { i() } +i () { j() } +j () {} A d() g() h() i() j() A d() g() h() i() j() B +h () { i() ...} + i() { super.i() ...} +k() { } k() B h() i() A d() g() h() i() j() B k() h() i() C +j () { k() } C j()

  27. Data flow anomaly A +d () +g () +h () +i () +j () def x use x A d() g() h() i() j() A d() g() h() i() j() B +h () +i () B h() i() def y use y It is an anomaly; not necessarily an error. E.g. if at the runtime the use of x in j() when it is called from B’s i() is actually unfeasible.

  28. Check the remaining anomalies yourself • State Defined Incorrectly (SDI) • Indirect Inconsistent State Definition (IISD) • Anomalous Construction Behavior 2 (ACB2) • Incomplete Construction (IC)

  29. Testing your OO programs • Intra-method testing (as in traditional unit-testing) • inter-method testing and intra-class testing. The latter is similar to the ADT approach. • Inter-class testing; this is perhaps closer to integration testing. • (were proposed by Harold – Rothermel, 1994) • The first three levels are usually not enough to expose errors related to access control, interaction through inheritance, and dynamic binding.

  30. Testing your OO programs • Due to dynamic bindingthe exact m called in f depends on the type of actual type of o • We can treat this as an integration testing problem  you do need to quantify over subclasses. f(x) { A o = FactoryA(x ) ; ... o.m() ; ... }

  31. Dynamic binding headache f(x) { A o = FactoryA(x ) ; // (1) o.m() ; // (2) ... o.n() } // (3) • It can get more complicated: m and n above may interact . Note that either m or n can be also be of the superclass of the actual class of o, if they are not overriden in o. • Again, just testing all possible (inter-methods) control flow paths will bound to explode. • see this as some form of integration  that is additionally also further affected by dynamic binding. • Previous integration testing  integration between m and f. Next concept  integration between m and n.

  32. Antecedent-consequent method pairs o.x = epxr • o is defined when one of its field is updated. The field o.x is “indirectly” defined (i-def) if the field is updated. Analogously, use and i-use. • Focus on coupling due to variables v (indirectly) def. by m, and used by n.  antecedent and consequent. • f itself is here called the coupling method. • We will limit to the cases where m and n target the same o (called context var), and only to v’s which are fields of o. f(x) { (1) A o = FactoryA(x ) ; (2) o.m() ; ... (3) o.n() } expr = ... o.x ...

  33. Antecedent-consequent method pairs • Coupling sequence C: a pair of antecedent m, and consequence n, such that there is at least 1x def-clear path from m to n with respect to some field o.x defined in m and used in n. • o.x is called a coupling var (of C) • The set of all coupling vars of C  coupling set. f(x) { (1) A o = FactoryA(x ) ; (2) o.m() ; ... (3) o.n() }

  34. With polymorphism the situation will now look like this... Notice how different types of the context o may give different coupling variables as well as coupling paths.

  35. Binding triple • Each coupling sequence induce one or more binding triples; each give you a test-requirement vs the polymorphism of the context o. • Each row above is called binding triple. Each may have more than one coupling vars, and each coupling var may have multiple coupling paths. A B C

  36. Now, complementary testing criteria for OO • (Def 7.53) All-Coupling-Sequences (ACS): for every coupling sequence c in f , TR includes at least one coupling path of c.  ignore polymorphism. • (Def 7.54) All-Poly-Classes (APC): for every binding triple b of c, TR includes at least one coupling path of b.  ignore that c may have multiple coupling vars. A B C

  37. Complementary testing criteria for OO • (Def 7.55) All-Coupling-Defs-Uses (ACDU): for every coupling var v of c, TR includes at least one of v’s coupling path. • (Def 7.56) All-Poly-Coupling-Defs-Uses (APCDU): for every coupling var v of every binding triple of c, TR includes at least one of v’s coupling path. A B C

More Related