The Test Auto Runner (AutoTDD) is an automated testing tool which helps you continuously monitor the status of your project by enabling you to automatically run tests on changes to your project. When a test fails, you will get instant feedback on what went wrong. AutoTDD also supports integration with CI tools such as GitHub Actions and Travis CI.
Metacello new
baseline: 'AutoTDD';
repository: 'github://hpi-swa-teaching/AutoTDD:master/packages';
onConflict: [:ex | ex allow];
load
You should now be able to open AutoTDD by clicking on Test Auto Runner via the Apps menu.
AutoTDD.sar
file from the project's Releases.AutoTDD.sar
into your image and select install SAR.You should now be able to open AutoTDD by clicking on Test Auto Runner via the Apps menu.
If you are upgrading from AutoTDD v2 or v3 please make sure to stop all currently running tests and close all AutoTDD-related windows before proceeding with the installation.
GitHub Actions tokens require repo and workflow permissions.
AutoTDD runs user-specified tests as soon as any relevant classes / methods undergo changes. As such, your tests will run quite frequently. Due to this, it is not advised to use AutoTDD for obtrusive or long-winded tests. This especially includes GUI tests where windows are opened / closed frequently.
AutoTDD supports customization for sounds as well as themes. To change what sounds AutoTDD uses, swap out the respective files in the
Resources/AutoTDD/sounds
directory and reload the sound player with:ATDDSoundPlayer new generateSoundMethods
AutoTDD also supports various color schemes depending on the currently selected theme in your image. To change the look and feel of the GUI, select a new theme from
Extras → Themes & Colors
A more detailed and technical documentation can either be found in the class comments under the AutoTDD Wiki.