I'm doing a unit test plan for the module manager -- issue #31. I've had a bit of experience with it, having built a module for my last issue (#43, changelog parser), but it'll still take a bit of exploring.
I was thinking of taking a sequential procedure approach to documenting tests -- e.g. a section for creating a new module, and within that a test for clicking the 'New' button, a test for selecting a module radio button and clicking the 'Next' button etc. It seemed to make more sense as a series of related tests like this would be conducted one after the other anyway; Rahul's unit test plan was very detailed but got a little complicated with all the structure, and I don't intend to have such a deep hierarchy in the plan. Tests documented in an order suitable for being carried out, and structured in a way that reflects this, should save some extra work making sense of the unit test plan for testers.
Please let me know if there's anything I should watch out for or some interesting things that can (intentionally) be achieved with the module manager.Create a unit test plan that identifies at least 25 specific tests and expected results that could be used to validate Joomla! v 1.5 development. The test plan should specifically list each action that would be taken by a tester and the expected results. A tester should be able to use the document to verify the accuracy of the Joomla! development.
I'm looking to have some sort of a draft available tomorrow to get some feedback on this new structure I'm trying out; please subscribe to this topic and watch your inbox if you're interested in having a look and posting some feedback.