Posts

Improve Your Testing Outcomes With synapseRT 9.6

synapseRT is here with its upgraded 9.6 version for Jira, packed with loads of new and interesting features to support the ever-evolving release processes of Agile teams and ensure enhanced testing efficiency. In an era of ever-decreasing release cycles, an effective test management process is absolutely critical to keep pace with an evolving Agile environment, while still maintaining a high standard of software quality in order to fulfill customer expectations. synapseRT 9.6 can provide your organization the flexibility to handle all aspects of your test management within Jira, while optimizing the speed and quality of testing to improve business outcomes.

New features, enhanced testing value

The 9.6 version can make your QA process simpler, faster and more efficient than ever before. Here’s a quick look at the new features:

  • Agile Integration: The execution of a test case can now be performed directly from Jira Agile board, thanks to the addition of a new feature called ‘Test Activities.’ This will facilitate faster execution of test plans and smoother management of all aspects of software quality.
  • Enhanced reporting: Access a range of new reports and gadgets that provide comprehensive information about your test library, issues reported during testing and test execution results. With improved visibility and insights into the quality, progress and overall status of your Jira projects, you can cut waste in the testing process and improve overall efficiency.
  • Basic Search’ for planning phase: With the new ‘Basic Search’ feature, it becomes more convenient to gather and select all needed test cases during planning phase.  
  • New JQLs: Search for issues in Jira like a pro and pinpoint exactly what you are looking for, thanks to the enhanced search functionality offered by new JQLs.
  • Improved ‘Add Attachment’ feature: Attach multiple files all at once during test execution and ensure more efficient time management.

With all these additions, you can give your test teams the flexibility, visibility, and insights they need to get even more efficient with test management and ensure accelerated delivery of better quality software as they rapidly scale Agile and DevOps. We have also fixed some bugs, so you will have a smoother experience.

To get a complete understanding of how synapseRT 9.6 works and how your Agile testing teams can leverage its features for enhanced testing outcomes, sign up for a live demo!

Drive Faster Time to Market with synapseRT 9.3

The increase in ALM tools in the market sans test management capabilities has surely upped the need for test management software or tools that can combine flexibility with traceability, usability, and transparency — arming your testers, developers, and QAs to take on any testing challenge. synapseRT is here with its upgraded 9.3 version for Jira, packed with interesting features that enhance traceability, assigning, and tracking — strengthening it as a holistic solution. synapseRT 9.3 comes with smarter and faster ways to manage requirements — import and export documents from others tools and numbering requirements for better traceability — and enhanced test plan and execution with an advanced search feature. Here’s a quick look at the new features:
  • Increase productivity with the brand new requirement import/export feature: You can now import and export entities like requirements, issues, tests, or steps from any other tool or platform in any format. Migrate requirements from other systems easily with requirement hierarchy and test case information maintained during the import.
  • Get enhanced traceability with the additional requirement numbering feature: You can now get an automated sequential numbering for your requirements (example: 1.1, 1.2, 1.2.1). This makes it easier to see the requirement structure and also makes requirement traceability more convenient. This is in addition to the requirement hierarchy that synapseRT already supported.
  • Quicker turn around with advanced search feature: You can now take advantage of the JQL (Jira Query Language) feature, which is the most powerful and flexible way to search for issues in Jira. synapseRT starts to leverage JQL to enhance search functionality in various of pages to give users a convenient way to filter a set of test cases and test executions. Filter test cases as per specific criteria, and add/remove them from test cycles.
With all these additions, synapseRT continues to be the most powerful test management tool within Jira available in the market. Get the latest version to empower your testers and developers better.

Four Factors to Consider While Choosing a Test Management Tool

As a tester, developer, or test manager, you must love shopping — specifically for test management tools? But the dilemma is that you have too many options, right? The pressure to vet software to make sure it is market ready is increasingly becoming complex and tricky, and vendors are not making it easy by providing a myriad of multifunctional test management solutions. Have you considered narrowing down your options with simple ‘what can it do for me’ pointers? Read more

Test case structures and other enhancements come to synapseRT NextGen 8.6

Many customers have told us they would like to see test case structure during the test execution. synapseRT NextGen 8.6 is out now with “Test Suite View” in the Test Cycle page! After collecting feedback from our customers, we’ve added other new features. Read more

synapseRT NextGen 8.5 is out now!

synapseRT NextGen 8.5 features a wide range of performance and stability improvements and sports all the feature additions of the five previous versions of synapseRT 8.x. In addition to merely boosting the performance and stability of synapseRT NextGen’s latest version, we’ve added some important new features and improved other product components.  Read more

Software Testing Magazine contributor prefers synapseRT add-on

Software testing is an important component in software development. It is difficult to efficiently develop new software without effective testing. Jira – one of the most popular tools for agile product development – helps development teams easily manage requirements, bugs, and tasks. Read more

synapseRT NextGen 8.4 is out now!

The much-awaited synapseRT NextGen 8.4 is out now with cool integrations and new features. Here is a quick rundown of what’s new: Read more

synapseRT NextGen 8.3 delivers the most requested enhancements

The new version of synapseRT NextGen, version 8.3, delivers new features and improvements that you’ve been requesting. At Go2Group, we strive to regularly update our products to meet the customers’ needs. In our latest version, released today (8/3/16), we’ve addressed many of our customers’ requests. Read more

The key features required in a good test management tool: Part 3 – test case execution

Having effective test management tools, and properly implementing and managing them, is an essential component of application development. In part one of this series, I explored test case management and tree structures. Read more

The key features required in a good test management tool: Test case execution plan

In part one of this series I described how important a test case tree structure is as a test management tool, and how using a tree structure can benefit a Quality Assurance (QA) team. In this blog, I will introduce the second important activity a QA team performs: the creation of a test case execution plan. A test case execution plan is created in the preparation phase of test execution. When the test case execution plan is well defined, the QA team is ready to begin work on test case execution, or testing. A test case execution plan normally includes a test scope, test assignment, schedule, and test environment. The ability to properly define and manage test case execution plans is an important feature for a test management tool.

Test scope

A test scope states what modules/features in the plan must be tested, or what kind of testing must be done. Examples of test scope include build verification, smoke testing, and regression testing. A test case is the basic unit employed to validate the product’s functionality. The QA team normally defines the test scope by choosing a set of test cases from a test case library. A good test case structure that is created using test cases in the library is necessary for the team to easily and effectively choose test cases. A tree structure provides a picture of product modules/features through its nodes, and can select multiple test cases by selecting any node. A tree structure is the best way to choose the test cases that define your test scope. It becomes especially important when you have a large number of test cases (1000 or more) in your test case library, and are preparing to execute at least ten percent of these cases in order to test several product features.

Test assignment

Once the scope of testing is well defined through a set of test cases, the next step is to consider who will take care of each test case during test execution. This task is called test assignment or task assignment. Normally a QA member manages many test cases, so “Bulk Assignment” should be supported in any test management tool. Bulk Assignment makes test assignment easier and saves time when planning tests.

Scheduling and forecasting

The user can monitor and manage the test execution process based on entered estimates and actual test times for each test case. Team resource information is normally clarified before testing starts, so if the management team can estimate the time required for testing, the entire test process can be easily controlled. Forecasting of testing time can be automatically output according to the formula: “Remaining Testing Effort = Estimated Testing Effort – Actual Spent Testing Effort.” Employing a good time management mechanism will help a management team finish its testing tasks on time.

Test environment

The test environment indicates what environments (OS, Browser, Build, etc.) are supposed to be covered in the test plan. The planned test cases from the test scope are usually executed against a specific test environment combination; for example, OS + Browser. As more and more testing is done with multiple test environments, it is good to see an approach that allows for multiple test runs stemming from a single test plan. Other attributes in a test plan, such as priority and risk management testing, may also be required, depending on the organizations or teams doing the testing. However, the most important components of a good test plan are those discussed in this blog. In the next post in this series, I will introduce the third key feature of a test management tool: test case execution.
Read the other parts in this series: Part 1 – The key features required in a good test management tool: Organizing test cases into a tree structure