In the information technology outsourcing world, a company has to its application being developed and maintained by others or framework is universal. When the vendor to complete this business, a common laboratory test is the transition activities as a whole. How do you design a traditional test acceptance criteria so that it can be tested and clear communication?
As a test, we usually discuss when an application is created and how to approach the test team within the company is in our own maintenance, but we rarely discuss what happens when from an outsourced provider to another change.
In the world of information technology outsourcing to a company that has been developing other people and maintain applications and architecture are common. When the vendor to complete the deal, involving the formation of contract management, real-time service levels, Committee on publishing content, and so on. The contract is part of a regular exchange activity test as a whole, both for infrastructure and applications.
Customers want is the ability to serve and the solutions they need to facilitate the documentation of the synthesis they can outsource part of their process, often to a higher price or a better strategy fit, did not bother to business.
I am a recent challenge in the application of this transition has test project manager. After another 90 applications are maintained by the company and we continue to maintain and develop this application. But before we do, the contract defines "traditional experiment" We had a pass. My task is to develop an acceptable standard on traditional tests and experiments may be clear communication.
What message is it?
Applications undue experimentation in test
In this test the contents, there are some special terms. The contracts define it as an experiment - not a test or testing.
There are a lot of similarities in the experimental testing and quality assurance. We provide a high level is an acceptable standard and were asked to identify and organize documents so that these things actually happen. Some special acceptance criteria can implement some simple changes in the system, upgrade the document, and the creation of cycle Cooperation Conference.
Traditional software development and job acceptance criteria, we can look forward to an acceptable standard functionality and business about the application - support activities. But here the acceptable standards are considered a project under test, so we were forced to take our experimental test stand.
One contract is to upgrade the system requirements document. This is a test case capture the following experiments: "The system description document has been upgraded yet?" We no longer go one step further and did not expect or actual results. It decided to test to assess if the document is indeed upgrade and improve our customers that we offer an upgrade documentation.
Note that we use open questions to allow a test to become an activity and performance, and testing the activity itself can be checked and outline rather than detailed list of supported scripts. It is precisely a "fair every thing" and "there is no other bad things to happen (as we know)," the event.
Acceptance criteria did not elaborate on whether the document is either upgraded or other details. What we can do is reference the original version is an upgraded version and then look at changes, at least in part the author. Again, a test preparation is not explicitly demand the implementation of experimental activities and put them re-written to be tested.
Read contracts issued a document or organized 65 activities, and does not require additional test management tool, I created an open question as each row in a spreadsheet. Then I built a four with a billboard version: done, progress has been made, and archived. Company and traditionally we have to provide evidence and documentation for each test activity.
Even with traditional methods to test analysis and test case management, team members found a lot of test cases covering the other but not the functionality of the application's code is a challenge. Even with a simple change to the system's activity has never been a change in the test itself - it can be painted on to the application pink, for all things. Test test is more about the ability to deliver a change rather than change itself.
We expect to see more transition experiments
Test lab outsourcing projects are increasingly common, not only considering the applications, but also for the IT infrastructure, IT support, and many other ideas. There is a clear trend is Linux, Windows, Oracle, and other technology is now being asked at least some of them publish their configuration and standardized test before use.
These techniques are usually looked at as a test to determine the activity, and they tend to use V- model of software development, each development phase there is a corresponding testing phase. The good news is testing is a matter of being asked, and we can begin discussions on how these tests, how to work as a test event we can learn not only the application of technology and architecture.
Traditional acceptable standard laboratory will become more frequent. As a test expert, we need to know to test an application and a job so that we may properly deliver a seamless transition in the difference between an application under the traditional experiments.