In a feedback for a (deleted) question I asked here last year, I was told that there is not easy way to do software testing. We may find prepared test cases for protocols but in most case the test are based on the requirement and most of them are for that reason unique.
Today I was preparing a thesis subject for a student, in field of automate testing (measurement technology, NOT software testing) but I also found the site Standardized Test Information Interchange.
This tells me that indeed there is some intention to somehow standardize software testing.
Therefore I'm interested in which automated test technology, standards, best practices shell be applied for a software development to stay on a maintainable course for a long run if no previous automated software testing solution blocks the free engineering decision.
The text of the original site mentioned in this question:
Interoperability – Standardized Test Information Interchange
Have you ever tried switching from one automated testing tool to another but decided not to make the move because you already had too much time invested and too many automated test cases that existed using the old solution?
Hundreds of automated software testing tools solutions currently exist and each provides their own development language for automating test cases. One tool might use VBScript; another might use a proprietary scripting language; while yet another might let you choose from a multitude of programming languages to create your automated test cases .
The challenge with this non-standardized way of automating test cases development across the automated testing tool community is there is no interoperability and no data exchange capability among automated testing solutions. If you wanted to switch from tool A to tool B you would have to recreate all your tests in tool B; no standardized approach exists to automate this process.
To address this and other interoperability challenges, we at IDT, along with others, have proposed a standard to the OMG (www.omg.org) called the Test Information Interchange for Automating Software Test Processes for software systems (in short TestIF).
The goal of this standard is to achieve a specification that defines the format for the exchange of test information between tools, applications, and systems that utilize it. The term “test information” is deliberately vague, because it includes the concepts of tests (test cases), test results, test scripts, test procedures, and other items that are normally documented as part of a software test effort.
The long term goal is to standardize the exchange of all test related artifacts produced or consumed as part of the testing process.