We would like to publish a dashboard of data from TestRail in IE/Sharepoint for managers outside of the QA group to see. 

I know there is nothing in TR for this as of yet (I know about the internal TR Dashboard).  I would like to ask those who have created dashboards for TR for external use on what they used, how they did it and how difficult it was to create.  We run the local TR instead of having it hosted as well.  We use Sharepoint internally so it would probably be best to use it rather than purchase more software.  We also use Visual Studio for app development (with C#).

I am not a programmer so I will need to provide the details of what we need to do and the queries to use.

Thanks for any suggestions/help/tips.
Brian

During test execution it is far easier to paste screenshots rather than attach a file (which then becomes a screenshot in testrail?!)

This feature would save me mucho time, sorry if already posted!

Regards
Simon - TA

A huge win for us would be to have the ability to create sub-test cases.

It is common for us to "stub out" a Test Suite with Test Case Titles and then go back and enter the actual test cases and/or expected results at a later date. It would be extremely helpful to be able to see if a test case already has steps and/or expected results defined without having to click Edit.  Perhaps, in the Test Suite, there could be two additional icons visible on the right hand side next to the Edit and Delete icons that would indicate the presence of a test case and/or expected results. The icon(s) only appear if the respective information exists.

Hi,

When writing some queries for statistics I noticed that TR stores dates as either Unix Epoch time or as an int.

Question I have is if the dates will be unified at some point in time or will the Test_Activities.Date field stay as int (storing as YYYYMMDD) and the Cases.created_on continue to be int but with Unix Epoch time?

Not sure what tables use Unix and which use the int with YYYYMMDD format - is there any docs on those tables and which format they use?

Thanks,

Brian

I am new to TestRail and I am looking how difficult it would be to integrate my automation to publish results to TestRail. One issue that I am facing is with ID"s for the TestRun. Each time I create new TestRun test id's change which means I would have to change id mapping in my automation as well. Am i missing something here or is there a different way of doing this. I would imagine TestID's would remain the same but TestRun ID would change or something like that. Any help would be appreciated.

I have been looking for ways to get only active test run ids and cannot find it. I have used get_runs in minapi but it gives me all the test runs. I did try to parse that json and see if it has any active flag in it but no. There is field called "is_completed" in there but it is not same as is active.
Can someone give me name of api that only gives me active test run ids when project id is given?
(PS: I have to use the old version 1 api.)
Thanks again.

Hi all,

I'm a relative newbie to TestRail so apologies if I'm asking a stupid question but can you add HTML into UI scripts?

I'm currently tasked with integrating our automation scripts with TestRail so that our test team can trigger the automated test cases from inside TestRail. I've got the basic stuff working (We can trigger tests and see the results in TestRail) but i'm now trying to expand it to make it more flexible. I'd like to be able to select the browser and browser version the test is to be run on from inside TestRail.

I imagine this user flow:
The tester clicks the <Run Tests> button, they then select the browser and version from some drop-downs and this is then sent to the trigger script. (I'll be passing the browser and browser version as URL parameters to the trigger script).

Does that make sense?

Thanks,

Alex

As I am using seperate steps in my testcases, I do not want the result of the total test to be set to passed before all teststeps have the status passed when I add test results.

Can I change the default value of the testresult, preferable to untested?

Will the end test result automatically adapt properly if a step goes on blocked, retest or failed, or if all steps are passed?

I know I am going to forget to adapt the total result. If it is set to passed, I might not look at it again. In other cases I will.

Hi,

Is there an easier way to have it put into TestRail once the problem is submitted in GTA?

As I posted elsewhere in another thread we're using Citrix GoToAssist Service Desk for reporting problems. I've gotten it configured here for reporting a bug and viewing but it seems a little kludgey in regards to how we'll have to file the bugs within TestRail, i.e. I fail a test and it pops up the GTA service associated with the project in another tab and then I have to copy/paste  the problem number into the TestRail window so it's linked to the GTA service associated with it for viewing it later.

Thanks for looking! If you need more information drop me an email Tobias/Dennis.

Mike

I have looked at the user guide for the Markdown syntax and I have noticed that there is no mention of creating tables.  In other guides there is a mention of creating tables but I have been unsuccessful in creating one.

I would love to use tables and so would my other team members.  I have had to use screenshots but there is no way to copy/paste from the Test Case into the application being tested.

Any hope this formatting syntax to be implemented or am I just incorrectly using the syntax.

Thanks,

Brian

Creating a custom field in TestRail.  Upon requesting a custom field type, the options are:
- Checkbox
- Date
- Dropdown
- Integer
- Milestone
- Multi-select
- Step Results
- String
- Text
- Url
- User

Interested in using a custom field type (Time Remaining on a test) that accepts days/minutes/hours (d/m/h); would one of these types apply and if so, how?

Conversely, as there are testrail fields for estimate and elapsed, is there a formula or field that displays/stores time remaining?  If there isn't then this custom field would apply.

Thanks!

I was creating a new subsection which would be the 6th 'level' in the group listing in the Test Suites and Cases screen.  I can create the subsection however I want to copy in some tests from another subsection (they are in the 5th 'level) but I can't copy the test cases. 

I can choose them and drag them to the new subsection but I can't get the subsection to be highlighted and drop them there.  When I try the test cases are still check marked in the original subsection and they are never moved (or copied) to the new subsection.

If there a limit to the depth of the group listing/subsections?

Thanks,

Brian

Hi, I am doing an evaluation of Test Rails for my company as we are considering switching.

I'm trying to do an import, and I get this error:

PCDATA invalid Char value 24 PCDATA invalid Char value 19 PCDATA invalid Char value 24 PCDATA invalid Char value 26 PCDATA invalid Char value 19 PCDATA invalid Char value 1 ...

Any help would be greatly appreciated as we'd like to prove that we can import our existing test cases and see how it looks in Test Rail as part of our eval.

Thanks!

Hello,

We are happy to announce the immediate availability of TestRail 4.0! This is a major release and we are really excited about the new version. 4.0 features a redesigned user interface, bulk editing for test cases, new powerful filter and grouping options, significantly improved navigation, baseline & single-suite support, new reporting options and much more. With more than 80+ new features, enhancements and fixes, this is our biggest TestRail release yet.

Make sure to also take a look at the blog posting to see the new features in action:

http://blog.gurock.com/postings/introdu … -4-0/2757/

Please also see below for a few important notes about updating to the new version.

What's new in TestRail 4.0
Please see below for the changes of this version.

• Added: Support for editing multiple cases in one step (bulk-edit)

• Added: Support for different suite modes per project (e.g. single suite, single suite + baselines or traditional multi suite mode)

• Added: Test suite baselines for more control over versioning test cases (including close support)

• Added: Cases > Activity Summary report which lists the new/updated test cases (e.g. within a specific time frame)

• Added: Redesigned todo page to display current workload of users (with a bar chart) and list of test runs

• Added: Todo mode for test runs which only shows the tests for a select set of users (in combination with the redesigned Todo page)

• Added: Sidebar is now resizable (width)

• Added: Tree on suite/run pages is now scrollable (independently of the page scroll behavior)

• Added: New view mode for suite/run pages to view a group including possible subgroups (i.e., a full subtree)

• Added: Toolbars on suite/run pages with options for changing the case/test sort order, column selection and various buttons

• Added: Filter on test suite/run pages for test cases/tests

• Added: Descriptions for sections

• Added: Additional tree column to Select & Copy/Move dialogs for test cases (also changed to compact view mode in the same step)

• Added: Copy/Move dialog is now fully resizable

• Added: Copy/Move dialog for test cases now supports the same filtering features as the Select dialog

• Added: Additional mode for Copy/Move dialog to copy/move the full section hierarchy (including empty parents)

• Added: Confirmation message to Copy/Move dialog before moving test cases (regarding possible test results that are about to be removed)

• Added: Support for deleting multiple test cases at once on test suite page (bulk-delete)

• Added: Keep current group/position on test suite page after editing the test suite/a test case or going back with the browser back button

• Added: Support for assigning all tests (using the current filter, if any) on test run page

• Added: Do not show all groups by default in the sidebar on suite/run pages if groups/levels exceed a certain threshold

• Added: Track and restore expand/collapse state on test suite/run pages for sections (in the sidebar)

• Added: Drag & drop for cases/sections now opens a popup menu when dropping the cases/sections (with Copy/Move actions)

• Added: Mode selection (all/any) for case/test/run filter popups on report forms

• Added: Steps control now displays the step/expected result boxes side by side depending on the browser width

• Added: Text boxes of steps control on case form are now resizable

• Added: Added Edit Case button to toolbar on test page to quickly edit the related test case

• Added: Tested By/On fields for tests including columns for test tables, filtering and support for Tests > Property Distribution report

• Added: Support for filters and pagination options in various read-based API methods (get_projects/get_milestones/get_plans/get_runs/get_cases/get_tests/get_results/get_results_for_case)

• Added: Offset parameter for add_result/add_result_for_case API methods

• Added: get_results_for_run API method to get the results for an entire run (more efficient than get_results/get_results_for_case for every test/case)

• Added: Tooltips for the most important actions (e.g. toolbar icons) (replace traditional browser hints which were used before)

• Added: JavaScript check to test plan form to ensure that a plan is not saved when JavaScript is not working properly

• Added: Action/link for reusing the description from the suite when adding/editing a test run (in the description hint)

• Added: Support for issue links for Jira_REST defect plugin

• Added: Support for custom fields of type 'Labels' for Jira_REST defect plugin

• Added: Increased default width of Push Defect dialog

• Added: Display first field on Push Defect dialog more prominently i.e. with a bigger font and input field (e.g. Summary field in Jira_REST defect plugin)

• Added: Disable Save/Add button after form submit on test plan form (to prevent double submits)

• Added: Support for UI scripts for form submits on test plan form

• Added: Show number of active/completed projects on dashboard page (sidebar)

• Added: Highlight currently selected page with border in pagination sections (e.g. for completed test runs)

• Added: Highlight currently selected report template in sidebar when creating/editing a report

• Added: On test suite page, highlight (change color) drag & drop action for current test case on hover

• Added: Display main form element more prominently, i.e. with a bigger font and input field (e.g. title or name) on case/suite/run/plan/milestone/report forms

• Added: Show welcome box on administration area overview page with quick links

• Added: Show prominent warning on administration area overview page if background task is not installed

• Added: Show message box on custom field add/edit form with hint about project assignments and link to documentation

• Added: Additional links and actions to help menu (for example, for TestRail's training videos or subscribing to the newsletter)

• Added: Support for SQL Server 2014 as database backend (Windows)

• Added: Support for Internet Explorer 11

• Changed: Redesigned test case selection on test run form to use a combination of radio buttons (include mode) and selection dialog

• Changed: Test runs and filter columns on Select dialog for runs (on report forms) can now be scrolled independently of each other

• Changed: Removed show-all mode for cases/tests on suite/run pages and added pagination to compact view mode

• Changed: Dynamically load cases/tests on test suite/run pages on page load

• Changed: Sidebar trees are now always sticky on suite/run pages

• Changed: Moved display mode selection to sidebar toolbar on suite/run pages

• Changed: Moved search to the top of the page, next to the user name

• Changed: Redesigned several aspects/elements of the user interfaces (e.g., headers, buttons, toolbars, colors, etc.) and modernized overall look & feel

• Changed: Improved usability of many existing dialogs and pages, e.g. by displaying actions more prominently

• Changed: Increased display limit for test details per user for Users > Workload Summary report

• Changed: Descriptions for checkbox custom fields are now truncated if necessary

• Changed: Don't display breadcrumb on pages where it doesn't add any additional value/context (with respect to the main/sidebar navigation)

• Changed: Pagination now uses Prev/Next text links instead of arrows for the previous/next actions

• Changed: Improved loading performance of test suite pages by on-demand drag & drop initialization (as opposed to initializing drag & drop on page load e.g.)

• Changed: Switched a single combined translation file for sys components (requires changes if a custom translation is used, see below)

• Changed: Ignore possible errors for dynamically loaded todos on dashboard/project pages (e.g. request-aborted errors when leaving the page before the todos could be loaded)

• Changed: 401 (Unauthorized) and 400 (Bad Request: invalid JSON, for example) responses by API now always include an error message

• Changed: Increased default height for default text fields (Steps, Expected Result and Preconditions)

• Changed: Increased size of review/confirmation dialog on test plan form

• Changed: Improved info message about client/server version mismatch (e.g., after updating an installation)

• Fixed: Sticky sidebar trees don't keep correct position when scrolling horizontally

• Fixed: Dropping a section on its parent raises an error if it's the last child and if there's more than one child section (on the test suite page)

• Fixed: Dropping a section on itself also selects this section (if previously unselected)

• Fixed: Adding/copying/moving a section to/within the sidebar tree expands all sections (now only the correct parent node is expanded, if any)

• Fixed: Completed tests may show the wrong set of attachments (for completed test runs)

• Fixed: Screenshot popups (fancybox) may be larger than the viewport size for large images

• Fixed: Attachments in the sidebar (e.g. on the test case page) may change their vertical position on hover (IE only)

• Fixed: Popup filter for runs/tests/cases on report forms may have a sub-optimal vertical position

• Fixed: Popup menus (e.g. add-result or changing the role on users overview page) may have a sub-optimal vertical position (e.g. outside the viewport)

• Fixed: In-Progress window is not toggled when clicking on the user name/progress link

• Fixed: Possible duplicate row error ('database_version') during an update from TestRail versions older than 2.3.

• Fixed: Assembla defect plugin does not support 204 No Content responses (for empty results)

Possibly breaking changes:

• Browsers: similar to most other applications we are dropping support for older web browsers in new releases from time to time. Specifically, we are dropping support for Internet Explorer 7.x and 8.x with TestRail 4.0. If you cannot upgrade Internet Explorer we recommend using Google Chrome to access TestRail.

• Translations: if you are using a custom translation for your TestRail installation, you may need to apply a few changes to your language files: http://docs.gurock.com/testrail-custom/ … stem_texts

• UI scripts: The new TestRail 4.0 version has a completely redesigned user interface and UI scripts get automatically disabled during the update. Please make sure to review your UI scripts for possible compatibility issues and update them as needed before enabling them again.

Getting the new version
A 30-day fully functional trial version of TestRail can be requested here (hosted on our servers or as download to install on your own server):

http://www.gurock.com/testrail/trial/

If you want to order TestRail, you can do so directly in our online shop:

http://www.gurock.com/order/

Registered customers can download the full version from our customer portal:

http://www.gurock.com/go/portal/

Updating to the new version
All accounts of TestRail Hosted already use the new version.

If you are using the download version of TestRail, you can update to the new version as usual by installing it over your existing TestRail installation (there's no need to uninstall your existing installation). The database upgrade wizard is automatically started when you access TestRail with your web browser. Please see the update instructions for details:

http://docs.gurock.com/testrail-admin/i … upgrading/

Please take the time to make a backup of your current installation before upgrading to the new version. In case you are using the old API module, please also make sure to update it to the current version:

http://docs.gurock.com/testrail-api/installation

Regards,
Tobias

The ToDo tab seems to have lost a lot of functionality for us.

I used the untested feature a lot to see what needs to be done for a certain test plan.

It would be really helpful if the results could be sorted by test plan.

We added a custom project_stats page to our TestRail install to show various metrics in realtime.

Unfortunately, we get an error now:

Trying to get property of non-object
---
Details: <missing>
File: /var/www/testrail/app/views/layout/header.php
Line: 180
Status Code: 500
Host: testrail-mobile.host.com
Uri: /index.php?/custom/project_stats/index/3 (GET)
---
Trace:
at errors::show (errors.php:53)
at ErrorHandler::error (header.php:180)
at unknown (loader.php:195)
at Loader_core->view_abs (loader.php:168)
at Loader_core->view (index.php:16)
at unknown (loader.php:195)
at Loader_core->view_abs (loader.php:168)
at Loader_core->view (loader.php:216)
at Loader_core->page (project_stats.php:58)
at Project_stats_controller->index (controller.php:106)
at Controller->_invoke_web (controller.php:74)
at Controller->_invoke (gizmo.php:101)
at require_once (index.php:106)
---
Version: 4.0.0.3249

Can you help us figure out what we are doing wrong? I can't inspect header.php to figure it out myself.

This is what we have in our custom page that appears to trigger the issue:

<?php
$header = array(
  'page_title' => "Project statistics ($project->name)",
  'page_section' => $project->name,
  'page_backlink' => true,
  'page_menu' => 'project',
  'page_project' => $project->id,
  'page_selected_menu' => 'metrics',
  'page_flash' => true,
  'page_breadcrumb' => array(
    'dashboard' => lang('pages_dashboard'),
    $project->name
  )
);

$GI->load->view('layout/header', $header);
?>

Thanks!

Thanks for this new release. You put a lot of effort into making TestRail even better, with lots of changes and improvements.

One of the features I was most curious about was the baseline support. Unfortunately, this feature does not work as I expected it. As it is implemented now, a baseline doesn't seem to be different from a normal test suite. If a baseline is created, all test cases are duplicated and are independent from the master. Changes to the master are not reflected in the baselines. I expected that baselines are just as links to the master. As soon as a test case is changed for a baseline, it becomes a new test case.

What is the suggested work flow for using a baseline? Shouldn't be duplicating test cases be prevented if it's not necessary?

Greetings,
Chris

My exported data contains meta data for each test case such as the ID in our old system (which I'd like to carry over as some tests reference other tests by this ID), created by, created on.  How can I import that?  I tried adding them as part of the case like this (just guessing on the names!):

<case>
<title>This is a test case title</title>
<type>functional</type>
<id>111270</id>
<created_by>cometgrrl</created_by>
<created_on>2014-03-17 00:00:00.0</created_on>
<priority>3</priority>

But when I import, they have a TR generated ID and the created by is my username and created on is the time of import.

Also, we are importing using <steps_separated> but we have a weird situation where our old tool has test data associated with each step/result pair.  I'm not sure how to import this in TR.  Is there anyway to add one more text box called "data" for each separate step?

At my workplace we create "New Feature" tickets in JIRA. Each one gets a new test plan made for it. Currently we manually make the test plan in JIRA (in plane text), then create it in Excel, then manually put it in another test software. This is a lot of manual data entry.

I want to know if TestRail will let me make a test plan for a New Feature ticket, and link the two somehow. Or alternatively, to automatically take tickets of a certain type (say "New Feature Test Plan") and create test plans in TestRail for them. Or any similar convenience.

Note this isn't for test results, but the plans themselves.

Thanks.