Targetprocess 3.2.8: Introducing Test Steps

Test Case Steps (new in Targetprocess 3!)

Test Case Steps is something that we haven't had available in Targetprocess v.2. This is a brand new entity introduced in Targetprocess 3. Test Cases can now be broken down into Test Steps.

With Test Steps, you can log very detailed instructions for Test Cases, if needed. Test steps can be added or removed by clicking 'Add step/result' links or a cross sign.

Next, now you can mark the exact  Test Step  where an error occurred in a Test Case Run. Test Case Run results are not tied to Test Step Run statuses. That is, all your Test Steps can be failed, but you would still be able to mark your Test Case Run as passed, if you want.

Test Steps can be imported from a .csv file ('Settings' - 'Import') as well, just as other Targetprocess entities. Remember to create or import Test Cases before importing Test Steps.

Important!

Old Test Case ‘Steps’ and ‘Success’ field are not used in Targetprocess anymore, they are still available in API but are going to be removed in the nearest future. This does not mean the data will be lost of course. During the upgrade both Steps and Success will be added to a special table in the new Description field. If you are using Steps and Success in Custom Reports, Import, Plugins, DSL Filters, Rest API or anywhere else - make sure you are ready for upcoming changes.

An alert message to Admin: no email notifications for their own actions

Now, while setting up email notifications, you’ll see an alert that you won’t be notified by email about your actions.

Bugs Fixed

• Cannot add Team Iteration if a required custom field for team iteration exists in a non-default Process
• Invalid URL is not resolved correctly: endless 'Initializing Application' stag