Early Exposure Test Results

sunglowmaizeMobile - Wireless

Dec 10, 2013 (3 years and 11 months ago)

89 views

Your Team

Name

Team Member Names







[Product n
ame

that you’re
testing
]








Early Exposure Test Results













Date





CSE 403
-

CSRocks Inc.






Your Team

Name

Team Member Names

Instructions

As the
customer of [Produc
t], you have been
asked to provide the
vendor
with some
user feedback

on an early rel
ease

of the

product. This feedback
will be formed by running a series
of

tests that you conduct on

[Product].


The
testing
serves three

purposes:

1.

It gives you the experience of being a tester of code that you do not
fully understand and cannot change.
This can be
both
challenging

and
rewarding
.

2.

It gives you the experien
ce of reporting bugs

in enough detail that a
developer can track down the problem.

3.

It gives concrete feedback to your vendor, at a time when it can still
have a positive effect on the fin
al version of their project.

Some notes on the testing:



Testing need only be conducted manually (the vendor is r
esponsible
for automated testing

and turning any of your tests into regression
tests if so desired)



Testing should be driven from the user inter
face

(web page

or android
emulator or android itself
)
. Your role is to act as a user of the tool
would act, and test user
driven
operations.




Do not test parts of the system that are documented as not yet
working. (However, by the release of a beta, signi
ficant functionality
should be present, and it should be possible to use the software in a
useful, even if limi
ted, way. If that isn't the case,
you should so
indicate in your assessment.)
Do not report duplicates of bugs or
missing features

that already a
ppear in the
release notes or
bug
tracking system.



There is really no end to how much time you can spend on test
ing.

Please allow yourselves
6
-
8

person hours

collectively
to conduct your
testing and report your
findings.
You
will want to
spread the
testi
ng

across
at least three

members
of your team

in an organized fashion
.




Please
report all bugs in the vendor’s
bug tracking

tool.
You will need
to get an a
ccount on their tool to do so.

Bugs can be

in the
b
asic
operation

or in the user interface design
or in the help or in the
Your Team

Name

Team Member Names

performance or ... the list of possibilities goes on



consult our class
material for ideas
.

We would expect you would
find a number of
things

(at least 5)

to report
at this point in the
development cycle
.



Your vendor may have par
ticular areas/useability features that they’d
especially like feedback on. Be sure to communicate with your
vendor to make the testing as valuable as possible.

Some notes on
[Product]
access:



Please work with your vendor to achieve access to an early rele
ase

(beta/beta+
)

of the product.
The vendor should provide you with
:

o

Directions to reach the front page of their product

o


S
ome informal release notes including

an outline of what they
expect to be working (test this) and no
t working (don’t test
this), any

interface questions, and

any directions for use.

o

Directions to reach their bug tracking system; which has
accounts for all members of your team

You should have access

to the beta
/
+

by Wed Feb 23
rd

at 11pm
.

Please l
et the staff

know if you have problems
with access.

You will be graded on the quality and thoroughness of

the

feedback you
provide

to the vendor
.

This is a team assignment, with all members
responsible for the team
submission.

Submit

the report

to
your vendor via email,
and

to

the 403 staff

via

the Turn
-
In
link on the class webpage
,

by
11pm by Monday February 28th
.



[Following page has template for results.]

Your Team

Name

Team Member Names

Summary of Findings

[Remove the Instructions Section prior to this. This section is what you
submit.]

Here you should give a

short
summar
y
(
about
2 paragraphs
: in general,

what
worked, what didn’t
, and
any

useability areas need to be improved
)
of your

test findings.
Focus on the overall/most impo
rtant findings.

[2 points]

You should have entered e
ach bug, be it a software bug, useability
issue,
feature request, performance problem, etc, into
the

vendor’s bug tracking
tool
. Please

provide the bug tool url and

list the bug

numbers

of the bug
reports that you entered.
We will be grad
ing your results by looking at
the
bug reports through the

tool.

[8 points]