= The Path Tools Framework = TODO: Keywords TODO: Description = How to Install = TODO: Configuration TODO: All-in-one one click image! Try it out = How to Use = TODO: Description text tools explained and tutorials == Tools == {{{ #!div class="gallery" {{{ #!div class="gallery_item" [[Image(pathProject.png, 150px, link=wiki:path:pathProject)]] {{{ #!div class="item_description" [wiki:path:pathProject PathProject] [[br]] Definition of the system under observation }}} }}} {{{ #!div class="gallery_item" [[Image(pathMap.png, 150px, link=wiki:path:pathMap)]] {{{ #!div class="item_description" [wiki:path:pathMap PathMap] [[br]] Extended test runner feedback }}} }}} {{{ #!div class="gallery_item" [[Image(pathFinder.png, 150px, link=wiki:path:pathFinder)]] {{{ #!div class="item_description" [wiki:path:pathFinder PathFinder] [[br]] Lightweight back-in-time debugger for test cases }}} }}} {{{ #!div class="gallery_item" [[Image(pathBrowser.png, 150px, link=wiki:path:pathBrowser)]] {{{ #!div class="item_description" [wiki:path:pathBrowser PathBrowser] [[br]] Connection of source code and hidden test knowledge }}} }}} {{{ #!div class="gallery_item" [[Image(pathView.png, 150px, link=wiki:path:pathView)]] {{{ #!div class="item_description" [wiki:path:pathView PathView] [[br]] Single-source and round-trip engineering code editor }}} }}} }}} == Tutorials == {{{ #!div class="gallery" {{{ #!div class="gallery_item" [[Image(tdfn.png, 150px, link=wiki:path:tutorial:tdfn)]] {{{ #!div class="item_description" [wiki:path:tutorial:tdfn Test-driven Fault Navigation] [[br]] integrates anomaly detection into a systematic breadth-first search for debugging failure causes back to defects. We answer important questions such as where to start, who understands failure causes best, what happened before failures, and which state properties are infected? }}} }}} {{{ #!div class="gallery_item" [[Image(backintime.png, 150px, link=wiki:path:tutorial:backintime)]] {{{ #!div class="item_description" [wiki:path:tutorial:backintime Back-in-time Debugging] [[br]] Follow execution histories from observable failures back to their root causes. This tutorial demonstrates how to apply PathFinder and all its debugging features step by step. }}} }}} {{{ #!div class="gallery_item" [[Image(tqf.png, 150px, link=wiki:path:tutorial:tqf)]] {{{ #!div class="item_description" [wiki:path:tutorial:tqf Test Quality Feedback] [[br]] TODO }}} }}} {{{ #!div class="gallery_item" [[Image(typeHarvesting.png, 150px, link=wiki:path:tutorial:typeHarvesting)]] {{{ #!div class="item_description" [wiki:path:tutorial:typeHarvesting Type Harvesting] [[br]] TODO }}} }}} {{{ #!div class="gallery_item" [[Image(modelbasedEditor.png, 150px, link=wiki:path:tutorial:modelbasedEditor)]] {{{ #!div class="item_description" [wiki:path:tutorial:modelbasedEditor Model-based Source Code Editing] [[br]] TODO }}} }}} {{{ #!div class="gallery_item" [[Image(traceability.png, 150px, link=wiki:path:tutorial:traceability)]] {{{ #!div class="item_description" [wiki:path:tutorial:traceability Requirements Traceability] [[br]] TODO }}} }}} }}} = Acknowledgments = The Path Tools Framework has been developed by [http://www.michaelperscheid.de Michael Perscheid] as part of his [http://opus.kobv.de/ubp/volltexte/2013/6815/ dissertation]. [[Image(media/icons/silk:user.png, title="Contributors", nolink)]] To date the following people also contributed to this project: * Franz Becker * Tim Felgentreff * Anton Gulenko * Markus Güntert * Michael Haupt * Vasily Kirilichev * Stephanie Platz * Oliver Richter * Leonhard Schweizer * Eric Seckler * Benjamin Siegmund * Bastian Steinert * Philipp Tessenow