Scribd
Upload
53 views

Business Features

This document provides an overview of the key features and functionality of the Bromine test management tool, including how to log in, create requirements and test cases, map requirements to test cases, schedule and run test runs, and view test results. It describes the planning, test lab, and reporting modules and how to add requirements, test cases, test steps, and upload test scripts within Bromine to manage the testing lifecycle.

Uploaded by

9391509391
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
53 views

Business Features

This document provides an overview of the key features and functionality of the Bromine test management tool, including how to log in, create requirements and test cases, map requirements to test cases, schedule and run test runs, and view test results. It describes the planning, test lab, and reporting modules and how to add requirements, test cases, test steps, and upload test scripts within Bromine to manage the testing lifecycle.

Uploaded by

9391509391
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

1.

Bu siness Features
This section will help you in understanding Bromine from usage point of view. How you can login, create requirements, test cases, modify or delete requirement, test cases, establish traceability between requirement and test cases, schedule your test run, test run process and test result process.

1.1.

Login

Open Bromine by navigating to the address where it is installed. If Bromine is installed or configured on a system or server, then ask your System Administrator for the path from where you can access it. For e.g. if you have installed Bromine in your local machine following the steps mentioned in this document, then just type http://localhost and you will see a Bromine Login Page. See below:

Once you login into the system, then you have to select the Project which has been allocated to you. You will see the list of only those projects in which you have access rights. After selecting the project, you will navigate to the Bromine Main Page (also called Workspace), from where you can now create your requirement, test cases etc.

1.2.

Planning Module

In the workspace area, you should see planning module, test lab module and Plugins (not a part of this document). The Planning Module is the starting point of defining the requirement and then creating Test Cases based on those requirements. Normally the Requirement should be created by Business Analyst and then the Test Team should start developing the Test Cases based on that requirement. But this might vary from Organization to Organization. As a best practice, it is always good to have requirements created by Business and then the Test Team should start writing their Test Cases.

This paper will also highlight the best practices when to start writing the Test Cases in Bromine. As you know that in Bromine you cannot manually execute the test cases, so ideally Bromine will only contain those test cases which can be automated.

1.2.1. Add Requirement


The first thing to start with Test Planning in Bromine is to write the Requirement using Add Requirement module of Bromine. Requirement is mainly your Business Requirement for which you have to develop the Test Cases. As a best practice start adding the requirement in Bromine as soon as you start writing the SRS or Use Cases. This will ensure that both Requirement and Test Cases development can be done in parallel. See the Requirement module page as shown below:

Provide the Name and description and parent. As a best practice, each Business Scenario can be named as requirement. For e.g. Validation for Invalid Login, Search Feature etc. can be called as

requirement. Provide the description which will help in developing the Test Cases. If the Child Requirement is derived from Parent, then provide the Parent Requirement for the Child. For e.g. You have a Parent Requirement of Login , when you will write the Valid and Invalid Login as requirement, then map it with parent which is Login. Creation of Requirement is not a mandatory step for writing the Test Cases but as a best practice it is a mandate to map each Test Case with a Requirement. This will ensure the Traceability between Requirement and Test Cases. One can edit or delete the requirement by opening the Requirement. To delete a requirement, open the requirement in Edit Mode and then click the Delete button. See the screen shots given below:

One can also define the OS/Browser Combination for each requirement. The above OS/Browser Matrix will be available after adding the requirement and then opening the requirement in Edit Mode.

1.2.2. Add Test Case


After Requirement comes the Test Cases. As soon as Requirement gets added, one can start developing the test cases on the basis of Requirement. To add the test cases, navigate to Planning>Add Test Case module. Refer the screen shot given below for the input required for Test Case writing:

Enter the Test Scenario in the Name field and give a small description (although not required). Select the Requirement to which this Test Case will map to. You can select multiple requirements as well as single requirement for the single test case. After the Test Cases have been created, then you can add the Test Steps and Upload the Test Script. As a best practice, one team creates the Test Cases and another Team generates the Test Script and then uploads the Test Script with their respective Test Cases. To generate the Test Script, the AUT should be made available. Generate your Test Script in Selenium and then convert it in either PHP or Java and upload the Test Script in Bromine. See the screen shots given below:

You can add your Test Steps in Action and Reaction Text Area. You can also arrange your Test Steps by doing a drag and drop. In case you want to delete the Test Case, use Delete Icon to Delete. Click

Upload New Test Script to Upload your Test Script file. This script will get in use when you will run your Test Cases from the Test Lab module. If you do not have any test script uploaded against the Test cases, then you cannot run your Test cases from the Test Lab module.

1.3.

Test Lab Module

The Test Lab Module helps you in running your Test Cases/Script. You can run your entire Test Suite from the test lab module. This Test Lab Module provides you the Project Overview in terms of Test Cases Failed, Passed and Not Run.

To run individual Test Script, select and open the Test Script from left navigation and then click Add to que Green Arrow. See the screen shot given below:

The Other Modules under Test Lab provide you with detailed results. Check the below module for explanation.

1.3.1. Latest Suites


This Module provides the statistical detail of Test Suite Run. It will give you the detail in terms of Passed Vs Failed Test Cases. You can also view each Test Run by clicking the View link under Action Column. See the screen shot given below.

1.3.2. Latest Tests


This module will again provide you the details, which you can view for reporting or analysis purpose. You can check the Result of your Test Run. This module displays both the Pass and Failed Test. This module is self explanatory. See the screen shot given below:

1.3.3. Latest Tests Failed


This module will display only the Failed Tests which you can check for doing your analysis and making your final report. See the screen shot given below. Most of the details are self explanatory.

1.3.4. Latest Tests Passed


This module will display only the Passed Tests, which you can check for doing your analysis and making your final report. See the screen shot given below. Most of the details are self explanatory.

You might also like