Hi,
I cant find any comprehensive documentation on testrail email notifications.
I know that emails are sent out to newly added testrail users. Can you possibly give me a list of scenarios where emails are sent from an admin point of view?
Eg. Are emails sent out when users are assigned/removed from project? When projects are marked as completed? When fields are added to a project?
It would be really nice from an auditing perspective if we could track changes made to test plans (or test runs). By changes, I mean the addition or subtraction of test cases or test suites (in the case of a test plan).:)
Hey again,
I'm trying to write a few UI scripts. Is it possible for me to access the data that testruns accesses to read "Total Runs Completed"? Or if not that, access the "# of tests Passed. # Blocked" etc? I just want to have my script display this data elsewhere. Doesn't matter where for now, just trying to access them in general.
Is it possible to change the default sort value for test runs to be by Status_ID? To give you a scale of what I want to reference it could pertain to either the individual grouping of test cases within a run to their status ID or the entire document of test runs to status ID.
I've tried two UI Scripts, one running App.Tables.group_by = 'cases:status_id'; and the other running App.Runs.setTestGrouping('tests:status_id');.
Currently neither of my scripts work. I'm not sure if that means I'm referencing these calls incorrectly(I'm not extremely familiar with javascript, learning as I go) , or if these are default values set by test rails that override my UI Scripts.
Any help would be appreciated.
I am trying to use the API and I am receiving an error: "Maximum POST size was exceeded".
my post looks like this:
/index.php?/miniapi/add_result/36908&key=mykey
{"status_id":1,"comment":"Automated Test Passed."}
Headers:
Accept: application/json
Content-Length: 66
Content-Type: application/x-www-form-urlencoded; charset=utf-8
etc...
I'm using FireFox 21.0
I've tried changing the Content-Type "application/json" to "application/x-www-form-urlencoded" but no change.
Any ideas of what the issue is?
I am trying to look into forecasting feature of TestRail and I have a questions.
1. Is forecasting based on test case estimate or based on elapsed time field or both? I can definitely ask the team to bulk update estimate filed. However getting the team to use elapsed as they run test will take some time.
2. does forecasting take into account the resources ?
Thanks
Ali
Hello,
I notice that when selecting what columns to display in the test run view, there are two columns which dont see to have any purpose
1. version
2. milestone
Both of these seems to be built in column are not in my testrail customizations. Even though test plan is part of my milestone, it doesn't show the milestone in this column. Am I doing something wrong?
Ali
Hi,
I would like to retrieve the value of a custom field from the last time a test was run to compare against the results of the current test run (we are intending on storing a performance test result in the custom field, and then automatically comparing it to see if there has been any significant degradation).
I can work out the ID for the test that I need to compare the data with, and I was hoping that
index.php?/miniapi/get_test/<test_id>
would give me the value of the custom field, but it isn't in the data returned from this call. I noticed that the comments and the defect list fields also aren't provided, and it would be good to be able to see these too.
Is there any way to get this information via HTTP?
Hi,
My testers have raised the following questions/feedback.
I think the answer to most of them is no, but please correct me if I'm wrong and consider these things for future releases.
1. When creating a test case, can the test step box size be configurable? Maybe make it bigger or make is an expandable box.
2. When creating a test case, ds there a keyboard step for adding a new step?
3. Can a Save and Cancel button be added to the top as well as the bottom of the add test case screen?
4. Is it possible to export a single test case or a group of test cases from within a Suite or Run?
5. When creating a Test Case, can we copy single/multiple test steps/expected results, rather than just the contents of one individual field?
6. When adding a Suite to a Plan/Run, the default option is to include all Test Cases in the Suite. This doesn't work for us and we'll always select the ones we want. Is there a way to prevent the default option from including everything, or at least making it clearer that all have been included?
7. Can the permissions be changed to allow individuals to delete just the things they have created?
Thanks
I'm working on an integration at the JSON API level that is running into some challenges. When we try to do a jquery ajax call, we receive errors that we can't call it because it doesn't exist on the same server. The alternative is using JSONP.
However, with JSONP, there is no way to set the Accept: header to application/json. The result is an ongoing error indicating that we haven't passed the right accept header. Is it truly critical to fail on this small detail, because it seems to be preventing us from integrating it into our defect system.
Thanks
Is there any where in TestRail that shows that a Test Case has been deleted? I can't seem to find a record of this happening.
Certainly deleting a Test Suite shows on the Project overview page, but while it may be hiding somewhere, I can't see a record if just a Test Case (or cases) has been deleted from a Test Suite.
I would note that currently only our Admin has the permission to delete Suites and Cases, but it would still be good to know that there was some indication within TestRail that such an event had occurred.
Neil
Are there plans to have reports that can be blessed and viewed without logging in to TestRail? I'm imagining a dashboard or view for developers who want to see test status but shouldn't need a license or account.
Thanks!
Hi,
i'm trying to set up a test plan.
How can i view or add the test suites ?
It should be in the sidebar, but i'cant see any.
What am i doing wrong ?
Thx
Marino
I know it's possible to customize the defect plugin to readout custom data from our defect logging software, but I had a question about the way TestRails looks up defect information.
Can I use information gathered by the defect plugin ( Any, but ours is OnTime ) in a UI Script or any sort of other instance? What I'm looking to do is check the defect readout for it's status "Open or Closed" and create a nice little UI Script printout that shows the user a table with the Open Defects only. If the defect is closed I'd simply ignore it.
I'm sure it's possible if I can access whatever method is pulling that defect data.
Hello,
I have a client using the redistributable console with our product.
They double-click saved logs files (text) to view them and when they close the console they get an application crash dialog from Windows Error Reporting.
Event Name: APPCRASH
Application Version: 3.3.2.49
Exception Code: c00000005
They also get a dialog that says EAccessViolation in module SmartInspectConsole.exe.
Have you seen this behavior before?
Thanks,
Sheri
In 2.7 you describe a way to customize the Add Test Result screen, however I don't see any instructions on how to do so.
How can I create a UI script and target it at that screen, or the Push Defect screen?
Thanks
I just noticed an upgrade of my Hosted Trial instance of Testrail to version 3.0.0.3009
Where can I find a release note
Thanks
Hello,
We are happy to announce the immediate availability of TestRail 3.0! This is a major release and we are really excited about the new version. It introduces many often requested features such as an all-new reporting area with 14 built-in report templates, great support for scheduling, sharing, and emailing reports, custom reports and much more. Also included is a new built-in API with a more consistent interface, lots of new and useful API methods and support for user permissions and authentication. We've also added new defect plugins for often requested issue trackers such as Assembla, Bitbucket, GitHub and Rally and also further improved the Jira integration.
Make sure to also take a look at the blog posting to see the new features in action:
http://blog.gurock.com/postings/testrai … ased/2399/
What's new in TestRail 3.0
Please see below for the changes of this version.
Added: Support for a new report engine and a new Reports tab which comes with several built-in report templates (see below) and full support for custom reports
Added: A report for showing the test case coverage for references/requirements (Cases: Coverage for References)
Added: A report for showing the property distribution for cases (Cases: Property Distribution)
Added: A report for showing the test cases with the highest amount of failed, passed etc. results (Cases: Status Tops)
Added: A report for showing a summary of defects for milestones, test plans or test runs (Defects: Summary)
Added: A report for showing a summary of defects per test case and for selected milestones, test plans or test runs (Defects: Summary for Cases)
Added: A report for showing a summary of defects per reference and for selected milestones, test plans or test runs (Defects: Summary for References)
Added: A report for showing the result coverage and comparison for test cases over multiple test runs in a coverage matrix (Results: Comparison for Cases)
Added: A report for showing the result coverage and comparison for references over multiple test runs in a coverage matrix (Results: Comparison for References)
Added: A report for showing the property distribution for tests & results (Results: Property Distribution)
Added: A report for showing the current workload for users (amount of tests and sum of estimates/forecasts) for selected milestones, test plans or test runs (Users: Workload Summary)
Added: A report for showing the summary/overview for a milestone (Summary: Milestone)
Added: A report for showing the summary/overview for a test plan (Summary: Plan)
Added: A report for showing the summary/overview for a project (Summary: Project)
Added: A report for showing the summary/overview for one or many test runs (Summary: Runs)
Added: Support for Internet Explorer 10
Added: Support for SQL Server 2012 and Windows Server 2012
Added: A new API which comes with various new methods. It uses a different address (api/v2) and calling conventions (entirely JSON-based) than the previous so called mini API. The old mini API is still supported but it is recommended to migrate to the new API.
Added: Option to Site Settings in administration area to enable/disable the new API (disabled by default)
Added: Options for changing the time frame for the activity line charts
Added: Charts are now customizable via UI scripts (allows to change colors, design, etc.)
Added: Charts are now JavaScript/SVG-based and no longer require Flash (better support for printing and mobile devices)
Added: Assembla defect plugin
Added: Bitbucket defect plugin
Added: GitHub defect plugin
Added: Rally defect plugin
Added: Pagination support for completed milestones on milestone overview (was "show all" previously)
Added: Pagination support for completed test runs on run overview (was "show all" previously)
Added: Pagination support for activity pages for test runs/plans and milestones
Added: Show announcement dialog on first request after updating to a new version with release notes etc.
Added: Also show amount of total tests in status charts (on run/plan/milestone pages)
Added: uiscripts variable now includes support for 'uiscripts.env' which contains details about the runtime environment (e.g., if running on Hosted and some base URLs)
Added: uiscripts variable now includes details about the current case, suite, test, run, plan or milestone (depending on the page)
Added: Support for text fields in Jira_REST defect plugin
Added: Support for user- and group-based custom fields in Jira_REST defect plugin
Added: Support for archived/released/overdue filters for versions in Jira_REST defect plugin
Added: Support for custom validating the Add Result dialog via UI scripts and a new JS event (e.g. to make the Version required)
Added: Hint to Integration page for projects that project-specific integration settings override the global settings
Added: Sections are now also included in breadcrumbs on case and test pages (and removed dashboard and current project in the same step)
Added: Support for adding images to steps and expected results (for (Steps custom field, on test case form)
Added: Support for adding images to expected results (for Step Results custom field, on Add Test Result dialog)
Added: Deleting a step now shows a confirmation dialog (on the test case form). Also changed the action order in the same step (to add/move/delete).
Changed: Background task now uses the configured language/locale/timezone for the installation
Changed: Background task now uses locking on the job level and not for the entire task (allows for more concurrency between the jobs, so that reports can be generated independently from sending email notifications, e.g.)
Changed: Display completed milestones grouped by completion date now (was a simple list previously)
Changed: Active and completed test runs are now displayed in the order as created/completed and grouped by the creation/completion date on the test runs overview (in small view mode)
Changed: Improved performance and reduced memory usage of activity pages for runs, plans and milestones (especially with many test results)
Changed: Improved performance and reduced memory usage of progress pages for runs, plans and milestones (especially with many test results)
Changed: Test plans can now also be started empty (ie. without test runs)
Changed: Labels of system statuses can now be changed (was only allowed for custom statuses previously)
Changed: Hint on Integration page in administration area for projects that override the global settings is now displayed more prominently
Changed: Reloading the Progress stats for tests no longer adds messages to the system log when the test is completed
Changed: Jira_REST defect plugin no longer includes sub-task issue types in Type dropdown
Changed: Action order for steps control (on test case form) is now add/move/delete (was move/add/delete previously)
Fixed: Jira_REST defect plugin only shows the first 50 users for user fields (e.g. Assignee)
Fixed: Jira_REST defect plugin may be slow for Jira installations with many projects (only when custom fields are used on the Push dialog)
Fixed: Checkboxes/drag icons may not be displayed in case and/or test tables (Firefox only)
Fixed: Error "Constant GI_ICON_DEFAULT_IDENT already defined" which may occur under rare circumstances after uploading an image, for example
Fixed: Reset icons for resetting the grouping in tables are not displayed if the table column width is configured too small to display the full column header
Fixed: User related tables are not dropped before applying a backup from TestRail Hosted (for migration purposes) which may lead to a "Primary key violated" error when applying a database backup (MySQL only)
Fixed: Possible "Invalid argument supplied for foreach()" error when viewing the history of a test case
Fixed: "Disable Forgot Password" and "Disable Invite User" options may accidentally get enabled when saving the site settings in the administration area
Fixed: Clickable area for Add Configuration dialog on test plan form/Select Configurations dialog is too small (Safari only)
Fixed: Possible SQL error in forecast background job ("The query processor ran out of stack space during query optimization") (SQL Server only)
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:
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
Now that TestRail 3.0 is out, we're excited to get it up and running but we have customizations we need to verify before we can launch it upon our users. Does our license provide for the ability to setup a sandbox environment for development & testing of customizations?
With version 3.0, does TestRail now support viewing defect status without mouseover? Is this now a piece of data that can be selected as a column (not just the defect ID)? Is this a data point that can be used in the new reporting section?
Specifically looking for the ability to map defect (JIRA) status to tests, group/filter/sort on it and display something like failed tests with defect status of resolved (for example). Is this functionality present in the stock reports, if not within the execution/definition interface of TestRail itself?
Either of these topics would go a long way towards this as well:
http://forum.gurock.com/topic/921
http://forum.gurock.com/topic/1251
We currently don't have a TestRail license, previously due to a few areas it was felt TestRail was lacking, but now it amounts to just this one item.
Our "required, but not yet there" list for TestRail is now:
Integration with JIRA for defect status without "mouseover" being required for retrieval (filter/sort/report alongside test information)
DONE IN 3.0 - Completed reporting interface, with ability to create custom reports and reasonable set of semi-flexible out of the box reports
DONE IN 3.0 - Completed API for automated tests and data retrieval/modification from outside systems
Features that are currently important/useful yet missing, though not required currently:
Better definition/documentation on "Forcast" predictions, how is determined, etc.
Access to Defect (JIRA) field data through UI Script
DONE IN 3.0 - Less Flash usage throughout, especially where navigation is concerned
DONE IN 3.0 - Standardized API type, inclusion in TestRil out of box, with documentation and user auth
DONE IN 3.0 - Custom naming of statuses (including system statuses)
DONE IN 3.0 - Out of the box "Daily Summary" type report (exec level, "pretty colors")
DONE IN 3.0 - Ability to email and/or print stats and aggregate information (report and/or within existing interface)