-Once we have identified Independently Testable Features, the next step is to - -2
-identify the Relevant Inputs for each one of these features. And there are - -3
-many ways to do that. So, what we're going to do, instead of - -4
-looking at them all, is that we're just going to focus on two different - -5
-ways of doing it. And they are fairly general ways. So, they - -6
-are applicable to a number of situations. And in addition, what I will - -7
-do, I will point you to other sources in which you can - -8
-look at different ways of doing this in the class notes. The problem - -9
-of identifying relevant inputs for some Software or some feature - -10
-of it is called Test Data Selection and can be expressed - -11
-as followed. Let's consider our software as usual we have - -12
-our Input Domain, which is the set of inputs for all - -13
-the software. And again as usual, we have our Output - -14
-Domain, which is the set of corresponding outlets for these inputs. - -15
-So the question here is, how can we select a meaningful - -16
-set of inputs in my domain? And of course corresponding outputs - -17
-because we know that test cases are an input, plus an - -18
-expected output. So how can we select interesting inputs for our - -19
-software? So a set of inputs that, after we run them - -20
-on the software, if the software behaves correctly, we'll have enough - -21
-confidence that the software is correctly implemented. So one possible idea - -22
-is, hey, why don't we just test them all? We just - -23
-do exhaustive testing. We do all the inputs, nowadays we have - -24
-powerful machines, we have a lot of computational power in the cloud. - -25
-Why not just doing it? So to answer that - -26
-question, what I'm going to do? I'm going to use another quiz. -- cgit 1.4.1