C. Ramey and B. Fox. Bash Reference Manual. O'Reilly & Associates, Sebastopol, CA, 2.2 edition, 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Table 1 shows the numbers of functions and lines of executable code in each version, and for each version after the rst, the number of functions changed for that version (modi ed or added to the version, or deleted from the preceding version) 3.2.1.2 Bash program characteristics. Bash [23], short for Bourne Again SHell , is a popular open source application that provides a command line interface to multiple Unix services. Bash was developed as emp server bash G4 497 292 G16 125 73 Table 2: Test Cases per Granularity Level. part of the GNU Project, adopting several features ....

....smallest possible test cases. We used the test cases from release 2.0 because they are the only ones that work across all releases. Second, to exercise functionality not covered by the original test suite, we created additional small test cases by considering the reference documentation for bash [23] as an informal speci cation. The resulting test suite has 1168 test cases, exercising an average of 64 of the functions across all the versions. Each test case in the new test suite contains between one and 54 lines. Each line constitutes an instruction consisting of bash or Expect [18] ....

C. Ramey and B. Fox. Bash Reference Manual. O'ReillyO'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

....1.07 217 89 Table 3: Test Suites. later versions of the system. Thus, the test cases from release 2.0 of the system were selected, because most of these test cases worked on all releases. This suite was then updated to test additional features (considering the reference documentation for Bash [29] as an informal specification) and increase coverage of functions. The characteristics of the test suites created for the four programs are presented in Table 3, and include the number of test cases in the suite, and the percentage of program functions covered by the test cases on the baseline ....

C. Ramey and B. Fox. Bash Reference Manual. O'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

....contained test cases that were obsolete for later versions of the system. As a result, we decided to use the test cases from release 2. 0 of the system because most of its cases worked on all releases, and we updated the suite to test more features (considering the reference documentation for Bash [28] as an informal speci cation) and increase coverage of functions. The characteristics of the test suites created for our four programs are presented in Table 3, and include the number of test cases in the suite, and the coverage of program functions achieved by the test cases on the baseline ....

C. Ramey and B. Fox. Bash Reference Manual. O'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

....faults in P to find an (approximate) optimal ordering for T . 4. 3 Experiment Materials For these experiments we utilized the bash subject program previously set up for experimentation as reported in [15] Bash is a popular shell that provides a command line interface to multiple Unix services [14]. As Table 1 shows, the latest versions of bash consist of over 50,000 lines of code and almost 2000 functions. Given the complexity and cost of preparing such a large subject for experimentation, we have invested significant effort in providing a supporting infrastructure so we can reuse the ....

....that accompanied bash release 2.0. We used the test cases from release 2.0 because they are the only ones that work across all releases. Second, to exercise functionality not covered by the original test suite, we created additional test cases by considering the reference documentation for bash [14] as an informal specification. The resulting test cases exercise an average of 64 of the functions across all the versions of the system. A second part of the infrastructure consists of a set of seeded faults created by a fault seeding process. Since we wished to evaluate the performance of ....

C. Ramey and B. Fox. Bash Reference Manual. O'Reilly & Associates, Sebastopol, CA, 2.2 edition, 1998.

....also contained test cases that were obsolete for later versions of the system. Thus, we decided to use the test cases from release 2. 0 of the system because most these worked on all releases, and we updated this suite to test additional features (considering the reference documentation for Bash [15] as an informal specification) and increase coverage of functions. Faults. We wished to evaluate the performance of prioritization with respect to detection of regression faults, that is, faults created in a program version as a result of the modifications that produced that version. Such faults ....

C. Ramey and B. Fox. Bash Reference Manual. O'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

....Table 1 shows the numbers of functions and lines of executable code in each version, and for each version after the first, the number of functions changed for that version (modified or added to the version, or deleted from the preceding version) 3.2.1.2 Bash program characteristics. Bash [23], short for Bourne Again SHell , is a popular open source application that provides a command line interface to multiple Unix services. Bash was developed as emp server bash G1 1985 1168 G4 497 292 G16 125 73 G64 32 19 Table 2: Test Cases per Granularity Level. part of the GNU Project, ....

....smallest possible test cases. We used the test cases from release 2.0 because they are the only ones that work across all releases. Second, to exercise functionality not covered by the original test suite, we created additional small test cases by considering the reference documentation for bash [23] as an informal specification. The resulting test suite has 1168 test cases, exercising an average of 64 of the functions across all the versions. Each test case in the new test suite contains between one and 54 lines. Each line constitutes an instruction consisting of bash or Expect [18] ....

C. Ramey and B. Fox. Bash Reference Manual. O'ReillyO'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

....of a lexical variable is given by the binding created by the innermost lexically enclosing construct declaring that variable. However, some programming languages still offer dynamic binding. The most widespread ones are Perl [67] T E X[36] Common Lisp [64] and Unix TM shells such as Bash [55]. As opposed to a lexical variable, which refers to the innermost lexically enclosing construct declaring it, a dynamic variable refers to the latest active dynamic binding that exists for that variable. 1 val y = 0; 2 3 fun showy (n : int) 4 ( print n; 5 print . The value of y is ; 6 ....

Chet Ramey and Brian Fox. Bash Reference Manual. Case Western Reserve University & Free Software Foundation, 2.0 edition, November 1996.

No context found.

C. Ramey and B. Fox. Bash Reference Manual. O'Reilly & Associates, Sebastopol, CA, 2.2 edition, 1998.

No context found.

C. Ramey and B. Fox. Bash Reference Manual. O'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

No context found.

C. Ramey and B. Fox. Bash Reference Manual. O'ReillyO'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

No context found.

C. Ramey and B. Fox. Bash Reference Manual. O'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

No context found.

C. Ramey and B. Fox. Bash Reference Manual. O'ReillyO'Reilly & Associates, Inc., Sebastopol, CA, 2.2 edition, 1998.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC