Fix TDD flow in Padre Testing
|Reported by:||kthakore||Owned by:||azawawi|
Current if a developer is doing Test Driven Development. They would try to do the following.
- Make a module
- Make a test that fails
- Click F5
- It will fail
- Hack and Click F5 again
Now this is broken because the
perl Build or make was never called so the new changes are not tested.
This causes the developer to go into cmd, build the module, and then test. This is not in the spirit of TDD and a major PITA.
To fix this I propose a new menu item in run which allows the developer to select a build method (dmake or perl Build) and have it run before any Test (single or complete) menu item.