-As you probably realized by now, at job development, it's a - -2
-lot about testing. So there is a lot of emphasis on - -3
-testing. Testing first, te, testing early. So that's the reason why - -4
-I also want to discuss what is the testing strategy in XP. - -5
-So first of all what is the basic principle? The basic - -6
-principle is that testing is Coded confidence. You write your test - -7
-cases and then you can run them anytime you want. And - -8
-if they pass, they'll give you confidence that your code is behaving - -9
-the way it's expected. If they don't pass on the other - -10
-hand, you'll know that there's something to fix. Another important concept is - -11
-that test might be isolated and automated. So both the running and - -12
-the checking of the tests has to be automated for all of - -13
-this to work. And there are two types of tests. The first - -14
-type of test is unit tests, that are created by the programmers, - -15
-and they're created by looking at the task cards. The task cards - -16
-describe what they implemented, functionality should - -17
-do, and therefore allows the developers. - -18
-The right test that can test this functionality. That can - -19
-check that the code's correctly implemented functionality. And as we - -20
-said, you should really test every meaninful feature. So, for - -21
-example, you should test every meaningful method in your classes. - -22
-You should put specific attention to possibly complex implementations, special - -23
-cases or specific problems that you might think of. while - -24
-reading the task cards. In some cases, when you do - -25
-refactoring, you might also want to write test cases specific - -26
-to that refactoring. But we'll say more about that. So this - -27
-was for the first kind of tests that are involved in - -28
-the, in the XP process. The second kind of tests are - -29
-the system tests, also called acceptance tests. And those tests involve - -30
-the customer. So basically what happens is that the customer provides - -31
-the test cases for their stores and then the development team - -32
-transforms those into actual automated tests. So these are tests created - -33
-by the developers. They run very quickly and they run very frequently. - -34
-These are tests developed with the help, with the - -35
-involvement of the customer they run longer. And run less - -36
-frequently, they run every time the system is integrated. - -37
-According to the cycle we saw a few minutes ago. -- cgit 1.4.1