We run the lint tests (and other we wrote like "are the visitor patterns implemented correctly?", "is the code you wrote following the design and coding conventions?" etc. before sending the package to integrate of making a new version of it... When doing tdd, having all test green does not mean you are done with the development and I think those type of test have to be run when development is done...
On Thu, Jun 3, 2010 at 3:41 PM, Noury Bouraqadi <[email protected]> wrote: > I'd like to add to my whishlist : an automated execution of lint when all > tests are green. > > Noury > On 3 juin 2010, at 21:07, Noury Bouraqadi wrote: > > > > > On 3 juin 2010, at 07:45, Stéphane Ducasse wrote: > > > >> > >> On Jun 2, 2010, at 11:22 PM, Germán Leiva wrote: > >> > >>> I'm thinking out load here ... > >>> > >>> In the debugger when a DNU is raised, for speeding up the programming > in "TDD mode": > >>> • The create button must add the method in the class of the > receiver, the possibility to choose a superclass of the receiver must be > optional (I don't like the recurrent asking...) in other button for example > or having different shortcuts from the keyboard > >> is it not already the case? > >> > > Only when the exception window shows up. Once you click on the debug > button, you can't do it anymore. > > > >>> > >>> • In the creation of a new class through "define new class" it will > be helpful to remember the last class category used > >>> Some ToDo list supported from the environment and some facility for the > creation of test. > > > > I'd rather go for a bit more sophisticated system based on Scrum task > board coupled with Monticello. > > Tasks descriptions are organized in three collections Done, ToDo and > inProgress. > > Once we do a project snapshot, we got these descriptions referenced in > the snapshot. So, when browsing the history of snapshot, one can more easily > figure out what each version is about. > > > > More features I'd like to have is in the refactoring browser : > > -When renaming an instance variable, rename its accessors two > > -Suggest to delete accessors when deleting an IV > > -Be able to generate accessors for multiple IVs at the same time (like in > eclipse!) > > -Have a preference that automatically generate accessors on addition of > IVs / class definition > > > > Noury > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
