To experience the full functionality of this website, you need JavaScript.
Test service progress details
Test planning
Requirements to be defined
The test complexity does not only depend on the components to test, e.g. the source code, but also on the requirements:
Norms and standards to be complied with
Test methods to be applied
Test environment
Scope of documentation
Utilized test environment
Cost and time estimation
The cost and duration of the implementation will be estimated when the source code is available and it is based on its complexity combined with the customer's requirements. For testing during the development process, the estimation is based on the estimated project size stated by the customer.
Test implementation
Test environment
The creation and execution of the tests will be done using Razorcat's own test tools or with the ones you are using. Therefore the utilized embedded compiler or the standard-compiler will be used. The test system will either consist of your hardware or of the PC simulation.
Test tools of Razorcat
The list of standard target compilers and debuggers/emulators supported by TESSY can be found at Supported development tools . If the debugger and compiler you are using is not supported by TESSY, we can adapt it if necessary.
Test creation
The test cases are created according to the customized test strategy and using available specifications and/or the source code.
Test strategy
We create a test strategy as part of the test plan which is adapted for your project including your requirements, requirements of standards and our test guideline.
Results and delivery
Documentation
Test specification
Specification of each test case, if requested using the classification tree method
Description of the intension of each test case.
Test result report
Includes the unit test specification
Test result report of each test case by comparing the expected and the actual values
Coverage report
Easy understandable representation
Test incident report
Unique ID number used to identify each issue which is found
Description of the cause and effect of errors
Recommendation for error correction
Additional documents
Test strategy
Test guidelines
Test plan (chapter about unit test )
Data
Entire test database for each source code file, so that the tests can be tracked and used for regression testing.
Configuration
Entire configuration of the used tools
Documentation for the reconstruction of the tests
Additional services by arrangement
Installation on-site
Consulting
TESSY license for the duration of the implementation phase
If your utilized compiler is not part of the matrix, send us an E-Mail .
Examples of errors detections
Deviations between the module design specification and the implementation
Missing or wrong implementation
Dead code (e.g. conditions that will not be achieved)
Memory violation (e.g. wrong memory section or wrong data type)
Overflow/underflow
NULL pointer access
Division by zero
Uninitialized variables
Infinite (endless) loop
C implementation error (e.g. using brackets, priority of operators)
C memory access fault (e.g. wrong, missing or implicit cast)
Compiler errors and warnings
Testing Service
You're interested in our testing service or have any questions? testing@razorcat.com form to request a testing service .
