Define, Share and Automate your tests / specifications

NEW - Collaborative tools       

Collaborative feature are available for a professional use of Tmar :
  • The « Tmar subclipse plugin » is a simple integration of Subclipse’s plugin main fonctions to make SVN accessible for all.
In fact only 4 fonctions are available from Tmar contextual menu :
 
Commit : Send changes from your local copy to the repository
Update : Update your local copy.
Revert : Undo all local edits.
Show History : explore records of every committed versions
  • Tmar eclipse also supports Tmar’s « working copies » feature.
You should use this feature, in addition to SVN, if your application is integrated in an automatic build factory :
 
Let’s consider this situation :

 

T0 : Your software product version #1 is already in production. It is secured by tens of Tmar        tests; your build factory tests status is completely « green ».
T1:  You will now work at version #2… which involves some specifications updates… and              therefore involves some Tmar tests modifications.
T2 : You start to modify some existant Tmar specification...
T3 : You want to commit your new specification, so that your developer colleague will be              able to manage the Groovy side of your Tmar tests.
Here is the problem : your build factory tests status will turn « red » !
The solution is to use Tmar « Working copies » feature
Let’s go back to step 2 :
T2 : You create a Tmar « Working copy » of your specification :Select the specification in Tmar                  navigator, then go to Tmar menu (or contextual menu) and select « Create working copy » 
T3 : You update the Tmar specification according to version #2 specification…
       As you feared, the test crashes :
T4 : you now do « SVN commit »  to send the working copy to SVN repository.
       Your build factory will remain « green » because Tmar working copy will not being taken into          account 
T5 : The developper uses « SVN update » to retreive the working copy.
       He fixes the application to reflect version #2 of the specification.
       He runs the test you were written… green !
T6 : The developper replaces the original copy using « Replace Original » action from Tmar menu              (or contextual menu)
T7 : The developper do « SVN Commit » for both the Tmar specification and the Groovy code.
       Your build factory is still « green »!
  • « Quick diff feature » will help you to check specification’s modification
To enable it, go to Tmar menu (or use toolbar icon) and select « Quick diff »
◦  Then select which reference to use for comparaison :
◦  You can now look Tmar editor left border to check modified lines, and even revert modifications :