Hi Sophie, thank you for clarifying this.
My current plans for TCS in QUASTe is to have it similar like for automated tests in the future: Holding the TCS's and give a possibility to add testresults of manual testing for a specific release. I really would appreciate to receive some specs, or ideas or whatever the community needs here. The Wiki-Page[1] could be a place-to-go for this. What do you think ? Best Regards Helge [1] http://wiki.services.openoffice.org/wiki/Quaste_TCS_Tool_Specification Sophie schrieb: > Hi Goran, > Goran Rakic wrote: >> У пет, 12. 02 2010. у 11:27 +0100, Helge Delfs пише: >>> new Test Case Specification tooling is released today. View my blog[1] >>> for further information. >> >> Hi Helge, >> >> What is a relation of the TCS to the TCM available at sunvirtuallab? > > There is no relation. TCS are done to tests new features, manually and > are used to make the scripts for automated tests mostly on dev builds. > TCM tests are for QA on l10n or RC builds to help to validate them as > stable. > But TCM maintenance is stalled and we miss several functionalities on > it, so it would be good to have a similar mechanism on QUASTe, replacing > TCM and have all in one place. That was what we talk about in Orvieto. > May be it's time to speak about again ? > > Kind regards > Sophie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- =============================================================== Sun Microsystems GmbH Helge Delfs Nagelsweg 55 Quality Assurance Engineer 20097 Hamburg OOo Team Lead Automation http://qa.openoffice.org mailto:[email protected] http://wiki.services.openoffice.org/wiki/User:Hde --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
