Concept Of Operations
Therefore, proper testing of Mapbuilder has to be done on the client side. The best approach is to automate the browser on the client side and observe the rendering of user commands or tests. The test runner simply matches actual results against expectations.
From a development standpoint, user stories are written first. Once approved by the PMC, they are further developed and test cases are (or should be) written before development starts (Test Driven Development).
This Wiki is used to develop user stories with input from MapBuilder Development Community.
It makes sense that a wiki be used for the test cases. Unfortunately, we cannot use the Confluence Wiki for local testing...
For MapBuilder Testing, Fitnesse has been selected as the Wiki used to develop the test cases and run the acceptance tests.
REMEMBER: In order to run the tests, the wiki has to run on the local machine to automate the client browser.
NOTE: The acceptance tests only run against Internet Explorer on a Windows Platform. This is a current limitation of the automation library. This limitation will be lifted hopefully very soon with the 2.0 version.