From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,53ca16c587912bce X-Google-Attributes: gid103376,public From: mfb@mbunix.mitre.org (Michael F Brenner) Subject: Re: Source files organisation using gnat Date: 1997/07/07 Message-ID: <5pqva3$9pi@top.mitre.org>#1/1 X-Deja-AN: 255258103 References: <19970630185901.OAA27670@ladder02.news.aol.com> <5p9jci$eb9@top.mitre.org> <33BAB415.6CCB@does.not.exist.com> Organization: The MITRE Corporation, Bedford Mass. Newsgroups: comp.lang.ada Summary: need some way to do regression tests Date: 1997-07-07T00:00:00+00:00 List-Id: Mike said: (f) now, before giving it to the users, run all the regression tests manually that were previously run at the bottom of each package in Ada-83. They are now separate executables. Wes said: the concept of having each package do its own regression tests as part of elaboration has merit in some circumstances. However, it is not a part of many standard development processes. So it is misleading to offer this step as if it were a necessary part of organizing source files into various directories (which is what the original question was about) Mike responds: If a standard development process does not have packages do their own regression test, then that standard development process should state where the regression tests are done instead. A development process without regression testing is incomplete. The benefit of the automated regression tests, during the period when they were possible, was that the process was automated, and therefore cheaper. You could tell with a quick search if the package body ended with the statements: BEGIN REGRESSION_TEST; END which automated quality checking of regression test occurrences (although you still had to manually check the DEPTH of the regression test, to make sure it verified that each required change still works). This is in accord with the original post and the original answer to the post that some of the configuration management features well used in Ada are either not universally possible anymore, or are not considered as important as they are. When a language feature automates a good programming practice, that is good (and economical).