Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ormf-dev] Testing guidelines, first draft
Hi,

Generally, this plan is applicable but I have some suggestions

According to me,

  1. Test Suite description must be more structural, test suit names may be modul names and sub names.
  • fulltest
    • Reuseable
    • description module
    • Attachment module (these names are not correct only example)
 we can construct new suit using existing suit and manage them easily.
  1. Ticket_<bugzilla‐id> --> Ticket_<testopia‐id> because test suite must be related only test cases. I think new issue or new bug must associate new or existing requirement or test case so we can obtain test coverage for release management.
Regards,
yahya



2008/10/21 Achim Lörke <achim@xxxxxxxxxx>

Hi

Attached is a very draft version of test design guidelines. I will add more text and graphics when I'm further done with the GUIdancer example project. Feel free to comment on every  part but keep in mind that the document will become much easier to understand once the example is finished (hopefully this week).

@ B., Yahya: Please look specifically into possibilities to connect our workflow to something like Testopia.

I have added two colleagues of mine to the recipients to get some feedback from "real testers".

Achim

<<Testing Guidelines for the Eclipse ORMF project.pdf>>

###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/

_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev




--
Saygılarımla
Yahya ÖZTÜRK

Back to the top