| Re: [ormf-dev] Test strategy |
Hi YahyaActually it's only an option. We could use another tool. Since GUIdancer is our product this would result in me dropping from the test job (but of course staying with ORMF). The decision on this is up to our project leads.
Yahya ÖZTÜRK wrote:
Hi,
I am reading all e-mail achives which includes ORMF testing topic and i understood
1) We will use GuiDancer for functional testing
Yes.
2) Achim will prepare testing strategy documantation and test project (guidancer import file)
Again, yes.
3) We must install GuiDancer and request license file for using GuiDancer
If it concerns GUIdancer please contact gdsupport@xxxxxxxxx. These guys are really good at giving support.
4) I can learn myself The GuiDancer with documantation and if i have more information i can request to assist from Achim
There are already a lot of test cases documented in the SVN repository. I will use those to create a first draft of a testing infrastructure inside GUIdancer.
5) Barbara prepare requirement and will publish it then we can create test case and documented it
We just talked about using test projects (actually fragments) and junit tests last Sunday. We agreed to write junit tests using white box scenarios to test as much of the non-GUI functions as possible and may use projects (not as fragments) to test the public interface of plug-ins (black box tests).
6) We can use JUnit for integration test but we dont talk about it anything
We will discuss this and document it for the team in the near future, but not in the paper I'm just writing.
@Barbara: is this correct?
Achim
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450
_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev