[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
That's what I had in mind. I'll ask one of our professional testers to
support Vasile and me in setting up a test strategy.
My previous email was just meant as a hint for all involved (or
interested) to start looking at the tool and not wait for the general
test design to complete. There is a lot to learn with GUIdancer (like
with every other tool aimed at complex problems).
Achim
Barbara Rosi-Schwartz wrote:
Hi Achim and thanks for all the pointers.
I just thought I would try and clarify the way J and I see functional
testing being tackled in I1 at least.
Seeing how you, Achim, have a lot of experience with functional testing
in general and know the ins and outs of GUIDancer in particular, our
suggestion is for you to actually take on the role of the lead in the
high level design of the testing strategy and the artefacts that you see
as being required for it. Vasile would then act under your lead to
design and implement real tests that follow your general strategy. At
least for iteration I1, we would envisage only the two of you being
involved with functional testing (with my initial contribution for
turning over what we have already as a starting point). Once the overall
strategy is laid out, the path forward is identified and a first set of
regression tests are in place (as complete as possible at this stage),
we could then discuss and decide how to distribute the efforts of
producing further tests moving forward beyond I1.
Is this consistent with your views and acceptable?
Thanks,
B.
On 29 Sep 2008, at 10:51, Achim Loerke wrote:
Barbara Rosi-Schwartz wrote:
Great stuff, thanks guys!
I will put a task in Bugzilla.
I will then get onto the test material as soon as I am done with the
project plan. My intention is to have the material ready for turn
over either at the end of Monday or some time Tuesday. Besides the
use cases themselves, it will be the whole set of (textual) test
scripts (with steps and verification points), a bunch of wrapper test
procedure documents and a set of control matrices. I will also write
an orientation document.
@Vasile and everyone interested in testing ORMF using GUIdancer:
please start by looking at www.guidancer.com, register yourself in the
shop and send an email to gdsupport@xxxxxxxxx stating that you will
use GUIdancer in an Eclipse project. You can then request a license
for using the tool on Eclipse projects. Use the tutorials and online
seminars to get yourself comfortable with the tool. Please contact me
for guidelines before starting to design "real" tests.
Achim
<Achim_Loerke.vcf>_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev
_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev
--
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
begin:vcard
fn;quoted-printable:Achim L=C3=B6rke
n;quoted-printable:L=C3=B6rke;Achim
org:Bredex GmbH
adr;quoted-printable:;;Mauernstra=C3=9Fe 33;Braunschweig;;38100;Germany
email;internet:Achim.Loerke@xxxxxxxxx
tel;work:+49 (531) 24330-0
tel;fax:+49 (531) 24330-99
x-mozilla-html:TRUE
url:http://www.bredex.de/
version:2.1
end:vcard
