Java-basiertes automatisiertes Test-Framework
| dc.contributor.author | Kalenborn, Axel | |
| dc.contributor.author | Will, Thomas | |
| dc.contributor.author | Thimm, Rouven | |
| dc.contributor.author | Raab, Jana | |
| dc.contributor.author | Fregin, Ronny | |
| dc.date.accessioned | 2018-01-16T08:55:03Z | |
| dc.date.available | 2018-01-16T08:55:03Z | |
| dc.date.issued | 2006 | |
| dc.description.abstract | KernpunkteManuelle Software Tests werden immer häufiger durch automatisierte Tests ergänzt bzw. ersetzen diese vollständig. Automatisierte Tests können jedoch nur in Komponenten verankert werden deren Quellcode vorliegt und sind daher für Fremdkomponenten nicht nutzbar.Der Beitrag beschreibt den „State-of-the-Art“ des Software Testens, definiert verschiedenen Test ansätze und würdigt diese kritisch.Die Grenzen automatisierter Software Tests werden aufgezeigt und das Problem der Testbarkeit externer Komponenten besprochen.Im CBTesten-Ansatz wird eine Möglichkeit zur nachträglichen Integration von Testroutinen in bereits kompilierte Softwarekomponenten vorgestellt.AbstractJava-based Automated Test-Framework With an increasing number of software-systems built using components, software developers are faced with entirely new challenges. For example, testing these modu-lar systems has become far more complex. Manual test approaches are incapable of dealing with the new architectures, leaving several parts of the systems untested. Thorough tests require extensive use of human resources, with enormous financial repercussions. Most customers are unwilling to accept these, completely unaware of their eventual benefit. Even existing automated software test approaches can only remedy these problems in parts. They commonly require source code access to add the necessary test routines, making the approach unsuitable for third party compo-nents. The innovative CBTesten approach tackles this problem. A highly dynamic framework is introduced into the software-system after compilation, which allows de-riving of test cases as well as fully automated tests based on the collected data. | |
| dc.identifier.pissn | 1861-8936 | |
| dc.identifier.uri | https://dl.gi.de/handle/20.500.12116/12626 | |
| dc.publisher | Springer | |
| dc.relation.ispartof | Wirtschaftsinformatik: Vol. 48, No. 6 | |
| dc.relation.ispartofseries | WIRTSCHAFTSINFORMATIK | |
| dc.subject | Arten von Softwaretests | |
| dc.subject | Automated Software Tests | |
| dc.subject | Automated Test-Case Creation | |
| dc.subject | Automatische Testfallaufzeichnung | |
| dc.subject | Automatisierter Softwaretest | |
| dc.subject | Bytecode-Injection | |
| dc.subject | ByteCode-Injektion | |
| dc.subject | Plugin-Based Framework | |
| dc.subject | Plugin-basiertes Framework | |
| dc.subject | Quellcodeunabhängigkeit | |
| dc.subject | Source Code Interdependence | |
| dc.subject | Test von Fremdkomponenten | |
| dc.subject | Third-Party-Components Tests | |
| dc.subject | Types of Software Tests | |
| dc.title | Java-basiertes automatisiertes Test-Framework | |
| dc.type | Text/Journal Article | |
| gi.citation.endPage | 445 | |
| gi.citation.startPage | 437 |