Opened 5 years ago

Last modified 2 years ago

#685 assigned task

Fix TDD flow in Padre Testing

Reported by: kthakore Owned by: azawawi
Priority: critical Milestone:
Component: plugins Version: 0.47
Keywords: Testing Cc:

Description

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.

Attachments (2)

menu_item.diff (1.2 KB) - added by kthakore 5 years ago.
Adds the TDD test menu item. Does nothing now though.
TDD_tests.diff (2.2 KB) - added by kthakore 5 years ago.
Runs perl Build test or make test, but needs windows fix to fine dmake, nmake so on

Download all attachments as: .zip

Change History (3)

Changed 5 years ago by kthakore

Adds the TDD test menu item. Does nothing now though.

Changed 5 years ago by kthakore

Runs perl Build test or make test, but needs windows fix to fine dmake, nmake so on

comment:1 Changed 2 years ago by azawawi

  • Component changed from editor to plugins
  • Owner set to azawawi
  • Priority changed from major to critical
  • Status changed from new to assigned

I agree we should give this a higher priority. We are lacking a lot in this part. I am moving this to a plugin soon. http://padre.perlide.org/trac/wiki/PadrePluginBuild

Note: See TracTickets for help on using tickets.