chris lukasiak wrote: Hi Chris,
i proudly present the new qa pages* as addition to the dba area - they contain (or will contain in future time) sections for different kinds of testcases and everything around this - the main idea behind it is to center the qa of structured manual testing in this point, make it better overviewable and shareable for better quality of oo.
My answer comes even later than André's, but better late than never ;-) In a word (or two) : Great idea
please support this project - the project contain many roles, from database beginners to specialists, from some minutes sparetime to ... we search for people from the community (not only oo qa): writing, reviewing and executing testcases (translate testcases). the results will be inputted into the tcm tool (bugtracking tool) after the process is cleared (comming soon).
How does this fit in with the TCM ? I think this is a very good idea, but isn't there a risk that we will be doubling our efforts, so to speak? I must admit to not having done the TCM tests in a while, I have been concentrating on getting the test tool to work instead.
I do like this idea, so there are definitely scenarios that can be developed for testing. I would have one question though : would it be possible to have some kind of db entry form for the results rather than having to e-mail them to you, with the inevitable mailbox overload that might cause ?
Just some initial thoughts, Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
