| Currently the IT test tool market is characterised by proprietary technologies and closed test systems. These systems lack test component reuse among different test tool vendors. |
Develop a generic testing infrastructure and testing architecture for TTCN-3 with open interfaces for test execution and for test management. Implement these interfaces in the tools and in the testing environments. |
| TTCN-3 is a new language that will be applicable to many new areas. However it does not include any methodology on how the notation should be used to systematically define tests for different application domains. |
Develop systematic testing methodologies and integrate testing tools into the methodologies. |
| Difficulty of defining of high quality tests from informal system specifications. |
Investigate the relationships of UML 2.0 testing profile and TTCN3. Formalise language constructs of TTCN3, UML2.0, MSC to enable production of TTCN3 based tests from UML models. |
| Current testing tools are lacking facilities for automatic test configuration, automatic test execution and test result analysis. |
Develop and implement test management tools covering the TTCN3 and UML2.0 testing profile. These tools shall also support open interfaces of the testing architecture. |
| Effort needed for test development is so high that industry is forced to accept poor test coverage with cost of decreased product quality. |
Develop automatic test case generation technologies for TTCN3 |
| Due to changing requirements or evolutionary system development process tests may become outdated and invalid. This causes lot of extra work in testing. |
Develop methods and prototype tools for test validation. |
| Currently software components are reused in many software intensive products. However, system functionality may differ so much that tests, which are developed traditionally, are not reusable for different products of the same domain |
Develop a methodology for reuse of test cases between products. |
| During software and system integration, many parts of the system may be replaced with different implementation. For example simulated component can be replaced with real HW or SW implementation. Changing interfaces and changing platforms force system integrators to redevelop tests for each phase of integration. |
Develop a methodology for reuse of test cases between testing phases. |
| People responsible in testing of a product do not want to spend efforts in making their test components available, understandable and reusable for others. |
Develop a process for test development for reuse. |
| Unsystematic way of reusing software may cause more harms than real benefits. Ad-hoc modifications easily lead us a situation, where we have to maintain separately multiple instances of same nearly same piece of code. Obviously this anti-pattern applies to reusable tests as well. |
Develop a process for test development with reuse. |
| Deploying and synchronising tests in a distributed test environment with tenths or hundreds of nodes under test is impractical to implement manually. |
Define test deployment methods and automatic test deployment tools for distributed TTCN-3 tests. |
| Most of the current test development and tester tools do not give any support in reusing a test component in other tester. |
Develop tools for test development and test execution, which support reuse and component based testers |
