Quick Start Guide

Welcome to Testnetic. Testnetic has been designed to help organisations tackle four key issues relating to software development:
  • Test Case Management – the storing of test case descriptions for quality assurance of software development
  • Testing – Executing one or a series of steps as defined by test cases.
  • Issue Tracking – Identifying and documenting task (or bugs) that have not been identified through a documented testing process.
  • Collaboration – Improving productivity via improved dialogue between testers, product managers and developers.
Testnetic has been designed from the ground up to comprehensively address these requirements in an intuitive, comprehensive and affordable hosted application. The index follows the sequence we could recommend to get started with Testnetic.


  1. Overview of Testing and issue tracking
  2. Creating and changing projects
  3. Creating a Test Suite
  4. Creating Test Cases
  5. Assigning a Test to a Test Suite
  6. Running a Test and a Test Suite
  7. Creating an Issue
  8. Using Activities

1. Overview of testing and issue tracking

Testnetic has been designed to support robust best practice testing whilst at the same time ensuring testing can be performed quickly and accurately in a collaborative environment. Testnetic’s approach and the terminology reflect current best practice with the key construct being: Project: Each project is totally unique to each other with no data exisiting between projects. Test Case: A documented set of things to do to validate a correct outcome. Includes procedure and expected outcome. Test Suite: A collection of Test Cases to test a particular component or environment. Test Library: All of the available tests that could be run either individually or as part of a test suite. Issue: Enables a task to be created that is not associated with a test. Can be a result of exploratory testing. Activities: All Issues and failed tested are automatically appear in Activities. Subsequently these can be rectified and retested as required.

2. Creating and changing projects

To separate clients, projects or major components of a simple application use Project. You can create as many projects as required. To swap between projects select the required project from the drop down list. Whenever you login make sure you are in the correct project. To create a new project select Create a Project. To add users select Manage Projects.

3. Creating a Test Suite

There are differing perspectives of how Test Suites should be employed, however for Testnetic it represents a collection of tests associated with a single component or process. A Test Case may be assigned to multiple Test Suites. It is also useful to create a General Test Suite. If you wish to add an Issue that is not tied to a particular Test Case (such as a typographical error) then it can be added to a Test Suite created for that purpose. For instance, a Test Suite called General or Miscellaneous could be created. The tester can create multiple Test Suites using the same test. For instance, one Test Suite might be testing using the Firefox browser and another might use the same tests with a Google Chrome browser. Test Suites, along with the Tests associated with it may be copied. Test may also be subsequently added and deleted from a Test Suite. This enables testing to be completed for different versions or test environments.

4. Creating Test Cases

As an application is developed typical there evolves a standard set of tests which ensure the quality of the development is maintained. A tests has two key elements; the procedure – how to perform the test, and the outcome – what is expected as a consequence of the test. Images can be added to further highlight the process. A Test can be run as part of an overall Test Suite, or as an individual test; selected from the Test Library. With paid accounts Test Cases may be imported as CSV files.

5. Assigning a Test to a Test Suite

Once tests have be created it is simple to add them to a Test Suite. The Tests will appear in the order they are added to a Test Suite. When a Test Suite is run, the Tests will be presented for testing in the order they were added to the Test Suite. Therefore it is important to ensure tests are added in the appropriate sequence for testing.

6. Running a Test

A test run may be conducted as a unique event or alternatively part of a Test Suite. a.) Running a single test: Go to Test Library, select the test you wish to perform and follow the steps outlined in the Test Procedure. b.) Run a series of tests: Often there is the requirement to test a complete component or module within an application. As discussed Test Suites are built to support these requirements. Select the required Test Suite and then the tests are presented as a series of tests.

7. Creating an Issue

Sometimes there is a need t0 create an issue to be that is not associated with a Test. For example you might identify a spelling error. We recommend creating a generic Test Suite called Miscellaneous. When an issue is identified, select that Test Suite from the drop down, document the issue and submit. This Issue is added to Tasks and can be attended to with other tasks.

8. Tasks

Any failed tests or issues are automatically added to Tasks. These can be assigned to a person, a due date, communications established between team members and a priority. Once completed they can assigned to re-test or deployed.

9. Communication with other team members

To avoid using email it is possible to communicate with other members within the application. If you type a comment and select a user those comments will appear in their comments drop down. Select Tasks from the menu and select the applicable task. Click in the “Select Users to Notify” and an option of all possible users will appear. Typing their name reduces the list size.