There is a lack of design documentation and specification in the
blueprints, creating test plans is problematic and requires a lot of
communication with the developers. I was wondering whether we could
partially remedy this by creating a place where we could share test
plans - a place to add comments, point out problems and figure out the
weak points of the features.
These test plans wouldn't be meant for documenting the
existing tests (documenting 800+ test cases would be impossible
anyway), just as a means of communication.
My current solution is github + text files[1]. I chose using github
because it's more likely to be actually used by developers. Another
alternative would be the wiki, but I think the code-like nature of test
plans would profit from using the same tools as for code. Putting them
right into the blueprints would be problematic, as it doesn't support
formatting, but we can link them there.
Are there perhaps some better solutions for this? Would it be worth our
time to try this?
[1] https://github.com/mkollaro/openstack-testplans
Martina Kollarova
--
irc: mkollaro
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
