What is Code Review?
Code Review is the process of examining the source code of a project by an unbiased engineer, to validate the design and implementation of a product at the most basic level.What is Whitebox Testing?
Whitebox Testing, or "Structural Testing," is the testing of a product in a way that references the source code in the testing process.Why do I need to run these sorts of tests?
Tests such as these are uniquely suited to find errors that may not appear in normal activation, or that appear in subtle or counterintuitive ways. Bugs found in Code Review can be fixed more quickly, as the specific code causing an error is discovered during testing: eliminating the need for your developers to hunt down what causes a problem. In addition, Code Review can be used to ensure that a consistent style of code is used throughout a project, allowing future changes to the code to happen more quickly.What is nResult's approach to Code Review and Whitebox testing?
At nResult we have developed a unique web based solution for exploring and testing Source Code. What was once seen as hundreds of pages of paper is now presented in a web browser: it is automatically organized, indexed, syntax highlighted, cross-referenced, and checked for common mistakes and possible trouble spots.
Before our tool was in place, training testers on a new product for whitebox testing could take weeks. Now we can often have our engineers up to speed on a product within 24 hours. This provides not only savings for our clients, but also gives us greater flexibility. Do you need twenty testers to do a complete test of your entire application by next Tuesday? We can do that.
One application that this is particularly well suited for is testing of game scripts: these are often developed in proprietary markup languages, with complex relationships between user actions and game events. Our software presents the tester with all the relevant information, so he can keep up with even the most fast-paced situations.
At nResult it doesn't matter if you develop in C, XML, Z-Code, or something unique to your lab. We will study every line, and find even the most subtle of errors.







