I am experimenting with Test Run at the moment and for the short time that I got to import my test cases (matching the test case format sample required), I would have to say I'm pretty happy with the experience.
However, we are using Atlassian markup within our test cases that are currently residing in JIRA and in there we have formatted our test cases using their table markup. I noticed that within your test case markup you don't have support for tables. The reason why we use tables is for test cases that have multiple test steps ..... we like to align a test step number with a description and an expected result. My work around in using the Test Run markup is to divy up the sections. The bad thing about this is that if you run into a test case with a number of test steps, the executor could get lost within the test case if he/she scrolls up and down the page.
Anyone out there know of a solution or work around at the moment?
******************** || Purpose: | The purpose of this test case is to verify that: * Changes made to an account after it is created is recorded. NOTE, after the account is created ...... creation of the account is NOT logged * Changes include: addition/deletion of emails and or devices, permission changes to the account. * Changes to the account are to identify which user account made the change and when the change was made, changes are real-time and immediate * Audit is searchable by either Account number of by Object * Audit is only available to Staff accounts and NOT Provider accounts * Start and End dates are considered in the audit * Help files are accessible|
|| Pre-Conditions: | * Staff access to Audit System Search * New account must be created for clean auditing|
|| Test Setup / Data: | none|
|| Step # || Description || Expected Result || | *Step#1* | Login with Provider account and verify that the *Audit System Search* widget is not available | Widget NOT available via *Accounts>Archive under Provider Account.| | *Step#2* | Create a new account under Provider of choice | New account is created and will now be used for auditing| | *Step#3* | Logout with Provider account and Login with Staff account and launch *Accounts>Archive>Audit System Search* widget| Widget is visible under Staff Account and Audit System Search dialog is displayed| | *Step#4* | Perform an audit on the newly created account number with valid start and end dates| You will notice that there are no results found because account creation is not logged| | *Step#5* | Edit the new account and temporarily *suspend* the account and check audit history| Account status was changed from active to suspended via *User* object.| | *Step#6* | Edit the new account and transition from *suspended* back to *active* then check audit history| Account status was changed from suspended back to active via *User* object.| | *Step#7* | Add a new email service to the account then check audit history| Account status was changed indicating the new *EmailAddress* object was created| | *Step#8* | Edit the email service by * updating the password * adding a *Forward to* address * adding a Vacation Message, then check audit history| Account status was changed indicating the following new objects * password update via *User* object * added *Forward to* address and Vacation message via *EmailAddress* object | *Step#9* | Add a new device to the account then check audit history| Account status was changed indicating the new *UserDevice* object was created.| | *Step#10* | Apply a new template to the account then check audit history| Account status was changed indicating the new *User* object was created.| | *Step#11* | Change Service Package to the account then check audit history| Account status was changed indicating the new *User* object was created.| | *Step#12* | Generate a device alarm for the account then check audit history| Account status was changed indicating the new *UserDevice* object was created.| | *Step#13* | Add or Remove any permission to the account and check audit history| Account status was changed indicating the new *User* object.| | *Step#14* | Edit the account and temporarily *cancel* the account and check audit history| Account status was changed from active to canceled via multiple objects (ie. *User*, *UserDevice* and *EmailAddress* objects if all are applicable.| | *Step#15* | Reactivate the account and check audit history| Account status was changed from canceled to active via *User* object.|
|| Tester's Notes:| none|
|| Pass/Fail Criteria:| The test case is considered a pass if * Changes made to an account after it is created is recorded after the account is created excluding the account creation * addition/deletion of emails and or devices, password/permission changes to the account are logged * identity of the user who performs the changes to the account are logged when the change was made, changes are real-time and immediate * Audit is searchable by either Account number of by Object * Audit is only available to Staff accounts and NOT Provider accounts * Start and End dates are considered in the audit * Help files are accessible|
I guess Atlassian is not supported yet, but straight HTML is, right?
Does anyone have an example of embedding an HTML table in a test case, just a real simple one. Using a table is nice for some more involved test cases with multiple steps and multiple verification points.