Print Page | Close Window

4-eye principle in unit Testing Printed From: One Stop Testing Category: Software Testing @ OneStopTesting Forum Name: Test Cases @ OneStopTesting Forum Discription: You must be well versed in writting Good Test Cases as they only will decide whether you can catch most of bugs or not. URL: http://forum.onestoptesting.com/forum_posts.asp?TID=545 Printed Date: 01Jan2025 at 5:11pm Topic: 4-eye principle in unit Testing Posted By: aradhana Subject: 4-eye principle in unit Testing Date Posted: 03Apr2007 at 12:20am What is "4-eye principle in Unit Testing"? The 4-eye principle ro 4-eyes principle is a term of workflow modeling. In a scenario under 4-eye principle, 2 activities are bound in a way that the person performing the first of these activities is not allowed to perform the second one also. The reason might be a law or an internal requirement. Usually the reason can be abstracted to the need to minimize errors in interactive process steps. For Unit Testing, the 4-eye principle means a developer should write his code (Activity#1), but he should not run the unit test of his code (Activity#2). His buddy should take on the job to run the unit test and they can exchange with eath other regularly. This can help that habitual thinking in a developer's design and coding will not crawl into the unit testing. However, a shortcoming of this approach is that the efficiency will be lower since the buddy maybe doesn't know the code as well as the developer and fail to create solid and effective unit test cases.

Print Page | Close Window