PROFIS Layout Office Field - Test Plan

Revision Author Date of Modification

1.0 Vamshi Priya T 27-Oct-2015

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 1 of 12
 Index

1 Introduction..................................................................................................................................4
1.1 Objective...........................................................................................................................4
1.2 Scope.................................................................................................................................4
2 Test Process Overview..................................................................................................................4
3 Features to be tested.....................................................................................................................6
4 Test Plan Strategy.........................................................................................................................7
4.1 Unit Testing.......................................................................................................................8
4.1.1 Objective...............................................................................................................8
4.1.2 Entry Criteria.........................................................................................................8
4.1.3 Exit Criteria...........................................................................................................8
4.2 Sanity Testing....................................................................................................................8
4.2.1 Entry Criteria.........................................................................................................8
4.2.2 Exit Criteria...........................................................................................................9
4.3 Functionality Testing.........................................................................................................9

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 2 of 12
 4.3.1 Objective...............................................................................................................9
4.3.2 Entry Criteria.........................................................................................................9
4.3.3 Exit Criteria...........................................................................................................9
4.4 Regression Testing............................................................................................................9
4.4.1 Objective...............................................................................................................9
4.4.2 Entry Criteria.........................................................................................................9
4.4.3 Exit Criteria...........................................................................................................9
4.5 System Testing..................................................................................................................9
4.5.1 Objective...............................................................................................................9
4.5.2 Entry Criteria.......................................................................................................10
4.5.3 Exit Criteria.........................................................................................................10
4.6 Performance Testing........................................................................................................10
4.7 Acceptance Testing.........................................................................................................10
4.8 Beta Testing.....................................................................................................................10
5 Test Report..................................................................................................................................10
6 Test Metrics................................................................................................................................11
7 Test Deliverables........................................................................................................................11
8 Risks and Assumptions...............................................................................................................11
8.1 Risks................................................................................................................................11
8.2 Assumptions....................................................................................................................11
9 Tools...........................................................................................................................................12

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 3 of 12
1 Introduction

1.1 Objective

Hercules is software, which shall be used by construction professionals. The Hercules software
would enable faster, accurate and easy to feed Total Stations with points, lines and arcs
information for field surveying/marking related works.

Hercules would enable the Field Construction Office with:

 Import/export files in DWG, DXF, CSV/TXT, and .HPL/.Hilti (POS format) formats
 Create
 Delete
 Move by an offset to Points, Lines and arcs
 Working with Layers

Field Construction office would also be able to view, edit or delete existing computations with
the same or different unit measurements like:
 Measurements of distances
 Angles
 Lengths

1.2 Scope

This document describes the scope, approach, objectives, resources and schedule for Hercules
application testing. It identifies:
 The items to be tested
 Items not to be tested
 Who will do the testing
 The test approach followed
 Pass/Fail criteria,
 The testing schedule

2 Test Process Overview

The following Figure 2.1 represents the overall flow of the Testing process:

 In the Requirements gathering and Analysis phase QA will validate the requirements for
correctness, completeness, and logically consistent.

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 4 of 12
  Design necessary and sufficient set of test cases to ensure that the design meet all the
requirements gathered.

 Review the test cases to ensure that all the features are covered. If there is a problem with
a test case, the requirements associated with the test case can be corrected or the test
cases will be redesigned.

Figure 2.1 QA Life Cycle

 Document the test case configuration, test data and expected results as required.

 Execute the test(s).

 Successful unit testing is required before the feature is eligible for component
integration/system testing.

 Unsuccessful testing requires a Bug Report Form to be generated. This document shall
describe the test case, the problem encountered, its possible cause, and the sequence of
events that led to the problem. It shall be used as a basis for later technical analysis.

 Test documents and reports shall be submitted. Any specifications to be reviewed,

revised, or updated shall be handled immediately.
Test Plan for PROFIS Layout Office Field
Confidential Document. Page 5 of 12
3 Features to be tested

Following are the features that are part of the application testing:
1. Data Management
a. Projects & Jobs
b. Importing Projects, Jobs, Files
2. Rendering
a. 2D Rendering
b. 3D Rendering
c. View Ports
3. Working with Points
a. Point Creation – Single Mode
b. Point Creation – Multiple Mode
4. Working with Lines
a. Drawing Lines
b. Drawing Poly Lines
5. Working with Arcs and Circles
a. Working with Arcs
b. Working with Circles
6. Attributes
7. Layer Management
8. Filtering
9. Transformation
10. COGO – 2D only
a. Calculating Distances
b. Calculating Angles
11. Reporting
12. Settings
13. Command Line Interface

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 6 of 12
4 Test Plan Strategy

Test strategy describes the different types of testing activities carried out as part of the Hercules
PC Layout application testing. It also provides the Test Entry / Exit Criteria for each level of
testing.

Following Figure 4.1 depicts the flow of testing strategy for Hercules application.

 Once the feature development is done, developer performs Unit testing before the code
check in.

 After successful Unit testing, code check in is done and build integration task is initiated.

 Successful build integration notifies an email and QA will pick up the build for testing.

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 7 of 12
 Figure 4.1 Test Strategy

 After receiving the build email QA will perform the Sanity Testing. To perform Sanity
testing QA will define set of basic tests to validate the build for further testing.

 Sanity testing successful means build is ready to perform Functional/Regression/System

Testing. If failed bugs will be reported to development team and build will be rejected.

 Any issues identified during further phases of testing will be reported to development
team and for the tracking purposes bugs will be raised in JIRA.

 Development team will fix the issues and the test process continues.

4.1 Unit Testing

4.1.1 Objective

Unit testing is to verify that the build is working as expected and it is ok to release to QA.
Development team will take care of running & maintaining the unit tests.

4.1.2 Entry Criteria

 Test cases are reviewed and ready to run

 Build is complete

4.1.3 Exit Criteria

 All planned test cases are executed

 Tests are working as per the expected results

4.2 Sanity Testing

Sanity testing is to make sure that the provided build is good to go and to start the functional
testing activity.

4.2.1 Entry Criteria

 All the Unit Test cases should be passed.

 Make sure that correct build is delivered to QA.
 Proper test data is ready to be used in tests.

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 8 of 12
4.2.2 Exit Criteria

 All results meeting agreed upon functionality and requirements.

4.3 Functionality Testing

4.3.1 Objective

To make sure that all the features are implemented and are working as per the design and giving
expected result.

4.3.2 Entry Criteria

 All the Unit and Sanity Test cases should be passed.

4.3.3 Exit Criteria

 All results meeting agreed upon functionality and requirements.

 Outstanding issues have been logged in Jira.

4.4 Regression Testing

4.4.1 Objective

Regression testing is carried out before going for system testing, which is to test old
functionality. Regression testing consists of running a set of standard tests to ensure that old
functionality has not been broken by new functionality. Regression tests are also run if a new
release is made after fixing a number of defects.

4.4.2 Entry Criteria

 Functional Testing is done

 Make sure that correct build is delivered to QA.

4.4.3 Exit Criteria

 All results meeting agreed upon functionality and requirements.

 Outstanding issues have been logged in Jira.

4.5 System Testing

4.5.1 Objective

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 9 of 12
System Testing is to verify that the all components integrated system is working fine as expected.
It is intended to validate the application as a whole. System testing also includes: installation,
uninstallation, functionality, usability, accuracy check, and recoverability.

4.5.2 Entry Criteria

 All test cases for the corresponding functionality and for end to end flow cases are
created, reviewed and ready.
 Integrated environment is setup to run tests.

4.5.3 Exit Criteria

 All the end-to-end flow test cases are working as per the expected result.

4.6 Performance Testing

Testing done to ensure that the application performs as per the agreed expectations (response
time, availability, portability, and scalability).

4.7 Acceptance Testing

Acceptance Testing is conducted to determine whether or not a system satisfies the acceptance
criteria and to enable the customer to determine whether or not to accept the system. Acceptance
testing ensures that customer requirements' objectives are met and that all components are
correctly included in a customer package.

4.8 Beta Testing

Beta Testing, done by the customer, using a pre-release version of the product to verify and
validate that the system meets business functional requirements. The purpose of beta testing is to
detect application faults, failures, and defects.

5 Test Report

For each report, the following information is provided:

 The build number of the application

 System configuration
 Test Results

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 10 of 12
6 Test Metrics

Following metrics will be captured and reported as part of the Test

 Summary Report
 Test Design effort
 Test execution effort
 Number of Test Cases executed
 Number of Defects and their classification
 Test Coverage (Number of test cases executed/Number planned)

7 Test Deliverables

Test deliverables are the artifacts, which are given to the stakeholders.
Following are the different types of Test Deliverables at different phases
 Test Plan
 Test cases Documents
 Test Data
 Test Results/Reports
 Test Summary Report
 Install/Configuration guides
 Defect Report
 Release notes

8 Risks and Assumptions

8.1 Risks

The following may impact the test cycle:

 Any new feature addition/modification to the application, which is not communicated in

advance.
 Any delay in the software delivery schedule including defect fixes.

8.2 Assumptions

 Every release to QA will accompany a release note specifying details of the features
implemented and its impact on the module under test.
 All "Show-Stopper" bugs receive immediate attention from the development team.

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 11 of 12
  All bugs found in a build of the software will be fixed and unit tested by the development
team before the next build is released
 In case of changes in the feature requirements, the test schedules may need to be
reviewed.

9 Tools

JIRA – Shall be used to manage the bug life cycle.

Zephyr – Zephyr for JIRA is an add-on application that provides cost-effective, highly
sophisticated test management capabilities.

Major features include:

 Create, view, edit and clone tests

 Plan test execution cycles
 Execute tests
 File defects
 Track quality metrics
 Create custom dashboards

Test Plan for PROFIS Layout Office Field

Confidential Document. Page 12 of 12