Andere Kunden interessierten sich auch für
![Advanced Slicing of Sequential and Concurrent Programs]( "Advanced Slicing of Sequential and Concurrent Programs")
Advanced Slicing of Sequential and Concurrent Programs51,99 €![Verification of Sequential and Concurrent Programs]( "Verification of Sequential and Concurrent Programs")
Verification of Sequential and Concurrent Programs74,99 €![Verification of Sequential and Concurrent Programs]( "Verification of Sequential and Concurrent Programs")
Verification of Sequential and Concurrent Programs59,99 €![Simplifying Runtime Verification of Distributed Programs]( "Simplifying Runtime Verification of Distributed Programs")
Simplifying Runtime Verification of Distributed Programs32,99 €![Critiquing Commercial Cattle Record-Keeping Programs]( "Critiquing Commercial Cattle Record-Keeping Programs")
Critiquing Commercial Cattle Record-Keeping Programs51,99 €![Advanced Software Testing V 2. 2e]( "Advanced Software Testing V 2. 2e")
Advanced Software Testing V 2. 2e49,99 €![JUnit Recipes: Practical Methods for Programmer Testing]( "JUnit Recipes: Practical Methods for Programmer Testing")
JUnit Recipes: Practical Methods for Programmer Testing54,99 €
Incremental, test-driven development is sweeping the
software industry, elevating testing from an
ancillary activity to an integral part of the
programming process. Unfortunately, in our recent
experience developing production programs in Java,
unit testing has only proven effective in assuring
the reliability of code with a single thread of
control; it is much less effective in concurrent
programs. To facilitate the development of concurrent
programs, we have developed:
1. An extension of the JUnit framework that actively
supports the developer by treating tests that could
silently ignore failures in auxiliary threads as test
errors;
2. A lightweight Java annotation language that can be
used to specify and check the threading invariants of
both existing and new code;
3. A testing framework that can record and analyze
the schedules of unit tests, detect deadlocks, and
run the tests using modified schedules, increasing
the likelihood that concurrency problems are discovered.
software industry, elevating testing from an
ancillary activity to an integral part of the
programming process. Unfortunately, in our recent
experience developing production programs in Java,
unit testing has only proven effective in assuring
the reliability of code with a single thread of
control; it is much less effective in concurrent
programs. To facilitate the development of concurrent
programs, we have developed:
1. An extension of the JUnit framework that actively
supports the developer by treating tests that could
silently ignore failures in auxiliary threads as test
errors;
2. A lightweight Java annotation language that can be
used to specify and check the threading invariants of
both existing and new code;
3. A testing framework that can record and analyze
the schedules of unit tests, detect deadlocks, and
run the tests using modified schedules, increasing
the likelihood that concurrency problems are discovered.