本文是我为公司设计和开发一个针对一些C++模块或共享库自动化测试工具而提出的一些设计概念,特此分享.
OverView
The Testing Engine is trying to provide fully automatic
API level unit
testingfor all the plugins/shared libraries which share some same specified APIs.
All the
values
in
the supported range
or list will be iteratively tested
toverify the handler set/get propertyfunction.
Its
target users are software developers.
It will
automatically
generate test report for the test cases you specified in a XML configuration file.
Software developer can utilize this tool to understand the software status and the development progress
.
Easy to Integrate
with
valgrind
to detect
and narrow-down memory leaks.
Easy to
detect core dumps for specific library or plugin.
Concept and flow by using the Testing Engine
Testing-DrivenDevelopment practice
Modularized
Unit test
for each module whose code have been finished
R
efactor
our design to be more
testable if necessary
Move to coding for next module once the previous module testing have been successful
Integrate to whole system, so that the software can be valuable to the whole software system.

Key concept of this tool/engine
Testing Configuration Management.
User can Constructand customize his/hertest cases via standard xml
Testing Execution: Automating the handler tests!
Refactor our designor add new features if necessary
Expose many bugs timely to developeratearly stage.
Improve people’s confidence about the software.
Testing Report Management.
Usercan get a detailed and accurate test report for each handler.
User can see the report viaLinux terminal directly: Error logs will be displayed in red.