Skip to main content
Skip table of contents

Version 8.4.0.1

New Features:

Time estimation & forecasting in testing

  • Enter time 'Estimate' for Test Cases
  • Enter actual time 'Effort' for Test Case Run
  • Time forecasting at Test Plan, Test Cycle & Test Case level

Integrate SynapseRT with CI tools: Jenkins & Bamboo


Reload test cases from a Active cycle

  • Any change in the test case after the test run is created from it will be prompted to user for reload

Learn More ...

Add more flexibilities when organize Test Cases from Test Suite

Bulk Clone support on Test Cases

  • Clone to create new Test Case/s from Test Suite/s

Learn More ...

Support of multiple Bug types

  • Can map more than one issue type as bug type

Learn More ...

New synapseRT Permission - 'Browse SynapseRT Panels'Improvements on 'SynapseRT Reports'

Learn More ...

External Test Case import

  • Import Test Case from external tool: TestLink
  • Interactive progress bar during Test Case import for better UX

Other improvements on UX

  • Defect bar is hyperlinked in Test Plan for quicker defect reference

  • Requirement key for associated Test Cases in Requirement issue are displayed to easily identify the rolled up test cases

  • Notification emails for 'Bulk Assign' on Test Runs are now consolidated to one email to avoid spamming

  • 'Run ID' column added on Test Case execution information from bug for quick reference on execution for developers

  • A 'Report Home' button added to reports for easy navigation

  • Improved reports with more synapse data and UX
  • Improved UX on gadget 'Test case Executions by Tester'

 

Release Notes

Story/Improvement

  • SYNAPSENG-1284 [SynapseRT Reports][Improvement]: There is no way to go back to 'SynapseRT Reports' home page directly from an report.
  • SYNAPSENG-1279 [Time Management][Test Case]: Put an 'estimate sample' in Test Case issue.
  • SYNAPSENG-1263 [Integration][Test Case]: Differentiate 'Execute' button in TestCycleDetails page for the Automation Run
  • SYNAPSENG-1260 [Integration]: Better to use 'Update' as button label in 'Edit Application' dialog.
  • SYNAPSENG-1255 [Test Suite]: User should stay at 'Free-form Test Cases' tab after 'Add to Test Suite' action.
  • SYNAPSENG-1253 [Configuration][Customer]: Add permission 'Browse SynapseRT Panels'.
  • SYNAPSENG-1251 [Configuration][Customer]: Allow user to map multiple issue types to 'SynapseRT Bug' issue type.
  • SYNAPSENG-1229 [Test Suite][Improvement] Highlight item if use puts mouse cursor to the item in the list.
  • SYNAPSENG-1217 [Time Management][Test Run]: Put an 'effort sample' in Test Run dialog.
  • SYNAPSENG-1212 [Test Plan][Requirement]: Add hyper link to 'Defect' bar in Test Plan issue.
  • SYNAPSENG-1196 [Requirement][Customer] Add 'Requirement' information for Test Cases in the list.
  • SYNAPSENG-1188 [Import/Export]: Display a progress bar when do Test Case import.
  • SYNAPSENG-1175 [Test Suite][Customer]: Support further action (Export/Move/Copy) from partially selected Test Cases in a Test Suite.
  • SYNAPSENG-1152 [Test Case][Improvement]: Test Suites should be in 'Collapsed' status by default when Add Test Suite from Test Case issue.
  • SYNAPSENG-1142 [Test Cycle]: Add an option for user to load the latest Test Case information from a 'ACTIVE' Test Cycle.
  • SYNAPSENG-1139 [Configuration]: Create validation for 'Maximum limit to Import Test cases' and 'Maximum Issue Result' with empty value.
  • SYNAPSENG-1105 [SynapseRT Reports][Improvement]: 'Test Plan' and 'Test Cycle' information should also be presented when 'Strategy = Specific Test Cycle '.
  • SYNAPSENG-1101 [SynapseRT Reports][Improvement]: 'Comments' column one of run attributes should be presented in 'Test Cycle Report'.
  • SYNAPSENG-1094 History section in Test Run to be in collapsed state by default
  • SYNAPSENG-1080 [SynpaseRT Reports][Improvement]: Add one more column 'Bug' in 'Test Plan Execution Report'.
  • SYNAPSENG-1011 [Improvement][Bug]: Add 'Run ID' column in 'Test Case' panel.
  • SYNAPSENG-974 [Gadgets][Improvement]: Improve UI to make 'Test case Executions by Tester' gadget more user friendly.
  • SYNAPSENG-964 [Test Suite][Improvement]: It is better to collapse all 'root' Test Suites by default in 'Move or Copy Test Suite' dialog.
  • SYNAPSENG-963 [Test Suite][Improvement]: We should support 'Move or Copy' part of Test Cases from Test Suites.
  • SYNAPSENG-962 [Test Suite][Improvement]: We should support 'Move or Copy' a Test Suite to be a ROOT Test Suite.
  • SYNAPSENG-919 [SynapseRT Reports]: Previous selection/value should not be cleaned for Requirement Report chart.
  • SYNAPSENG-912 [Import/Export][Improvement]: Adjust the sequence of columns to make it more suitable for 'Test Case' issue.
  • SYNAPSENG-888 Import data from other test management tool to synapseRT NextGen.
  • SYNAPSENG-805 [Email Notification]: Notification emails for 'Bulk Assign' should be combined to be only one email
  • SYNAPSENG-673 [Customer's Request] Integrate SynapseRT with Jenkins or other external systems.
  • SYNAPSENG-465 [Customer] Time estimation for test plan and test execution prediction.
  • SYNAPSENG-304 Improvement: add hyper link to progress bar and pie chart from test plan level.

Bug Fixes:

  • SYNAPSENG-1338 [Test Plan]: 'Add Requirement' is not going to add its aggregated Test Cases, instead, only directly associated Test Cases can be added.
  • SYNAPSENG-1328 [REST API][Customer]: 'testCaseKey' is not returned from 'GET /rest/synapse/latest/public/testPlan/{testPlanIssueKey}/cycle/{cycleName}/testRuns'.
  • SYNAPSENG-1316 [Test Cycle]: Defect number should come from test case level instead of test step level.
  • SYNAPSENG-1281 [Test Plan][Customer]: Pagination link is not showing up for OLD data (Test Plan).
  • SYNAPSENG-1257 [SynapseRT Reports]: There is no validation to 'JQL' field for 'Requirement Coverage Report'.
  • SYNAPSENG-1254 [Test Suite]: There is no warning message if click on 'Add to Test Suite' button without selecting any Test Cases from the list.
  • SYNAPSENG-1243 [Test Case][JIRA7.2.x] Drag&Drop doesn't work if open a Test Case from JIRA filter (in Detail View mode).
  • SYNAPSENG-1228 [Test Case][Customer] Import 'Test Step' has some problem.
  • SYNAPSENG-1213 [REST API][Customer]: Time stampe from execution history is not changed if update Test Run with same result.
  • SYNAPSENG-1202 [Test Case][Customer]: Field-length is not limited for long strings - broken view.
  • SYNAPSENG-1183 [Traceability]: Test results from 'ABORTED' Test Cycle are still visible in Traceability matrix.
  • SYNAPSENG-1182 [Import/Export][Test Suites]: 'Test Suite' information is not generated in exported file if the Test Case comes from other project.
  • SYNAPSENG-1181 [Manage REQs]: Drag the last item in the list and drop it to any other item (to be a child), will cause its parent disappears in from the list.
  • SYNAPSENG-1176 [Test Suite]: Test Case number label is not updated immediately if a child Test Suite with some Test Cases are removed.
  • SYNAPSENG-1163 [Test Suite]: If there are only one Test Suite in a 'Root Test Suite', its 'Child Test Suite' cannot be moved out from the parent node.
  • SYNAPSENG-1153 [Import/Export]: A redundant space / missing a space in error message.
  • SYNAPSENG-1150 [JIRA7.2][SynapseRT Reports]: 'Test Plan Execution Report' cannot generate data from any Test Plan except the first created one.
  • SYNAPSENG-1145 [Import/Export]: Test Case sequence in exported file is different with how it organized in Test Suite.
  • SYNAPSENG-1136 [Test Case]: Line breaks are not handled well in when export Test Case from JIRA search.
  • SYNAPSENG-1135 [SynpaseRT Reports][Customer]: Line breaks are not handled well in 'Test Cycle Report'.
  • SYNAPSENG-1126 [Test Case][Customer]: 'Create Issue' is not refreshed to 'Test Case' issue type when add Test Case from Test Suite, instead, it comes from previous selected issue type.
  • SYNAPSENG-1106 [Test Suite][Import/Export]: The Test Suite path always shows the 1st one if a Test Case is associated to multiple Test Suites.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.