This is very relevant for testing activities since it is not uncommon for
an application developer to spend more than half of his day in testing: specifying tests,
executing them, and making corrections.
Testing is Done by Experienced Developers The experienced developers
who created the DSM solution have already done some testing. The errors prevented
by the rules and constraints of the modeling language don??™t need to be tested again. In
a similar vein, the automated generation of code reduces the testing needs of
developers. We discuss the testing of DSM later in Part IV.
Naturally, all errors don??™t disappear with DSM, but their prevention and correction
is left to the more experienced developers in the company. The nature of the errors is
also different from that of manual practices. In DSM, they tend to be more consistent
rather than random as in manually written code. In DSM when an application
developer ?¬?nds an error, he can most likely correct it by changing the model. If an error
is found in the generated code, the correction should be made in the generator instead
of correcting just the particular application under development. This allows other
application developers and other design models to bene?¬?t from the corrections.
What is Tested? The kinds of testing targets that are usually handled manually
can be partly covered automatically by DSM.
Pages:
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76