Open ndemengel opened 12 years ago
Yeah customizing the assertions templates would be great, after all it was the intent of assertion generator.
Let's start without profiles, I think it's too much for the time being.
Question : In #5 we were talking about letting user change the generated assertions class name with a popup. I'm wondering if this is still useful if user can change the template. WDYT ?
Indeed. I would say that it depends whether we want to offer the user the ability to change the name "globally" or on a "per-case" basis.
I think "globally" should be enough, I don't see a use case where, after having changed the templates, a user would also like to change again the class name, but if someone comes up with a real-life use case then we will do it.
I think it would great change template globally (in Preferences) and per-case.
The assertion generator lets the user modify assertion templates. The plugin preferences could provide a way to edit those templates (much like JDT does for Java code templates).
Additionally, one can imagine that several template profiles could be configurable, so that different projects or classes could use one or the other, but that might be too much customization for such a basic tool.