It's all about data
In my experience, getting the standard tests working on your code is mainly about getting the test fixture right, as in the previous exercise. Fixing the error by supplementing the fixture isn't a coincidence. It's the most probable thing that you will be doing in getting the standard tests run on your code: bring the test fixture in the right state.
In this specific case, we fixed the fresh fixture. Running more standard tests will show other kinds of test errors. Solving these errors, however, is again mostly about updating the test fixture, fresh and, in some cases, shared fixture.
Executing and fixing Tests-Fixed Asset
Having run only one standard test app – Tests-VAT – let's see the results of running another one against our code: Tests-Fixed Asset. Some of those failures relate to the LookupValue extension. Apparently, the fix we implemented to tackle the errors thrown on the Tests-VAT test run did not prevent the...
