Skip to content

Acceptance testing #66

Closed
nielsAD opened this Issue May 21, 2012 · 5 comments

4 participants

@nielsAD
Collaborator
nielsAD commented May 21, 2012

Acceptance testing for the client. Report your testing method and findings. File bugs where appropriate.

@FelixAkk FelixAkk was assigned May 21, 2012
@FelixAkk
Owner
FelixAkk commented Jun 2, 2012

So I wrote it down in acceptance_testing.tex under deliverables\final-doc but this is probably not the best place. Also it's as a stand alone document as it is. It could also use some more scenarios. Feedback plox!

@FelixAkk FelixAkk closed this Jun 4, 2012
@jieter
Collaborator
jieter commented Jun 8, 2012

Is there some report about your findings? I think it makes sense to run the acceptance tests, write a small report about it, and run it again next week (and report about it)...

@FelixAkk
Owner
FelixAkk commented Jun 8, 2012

Haven't really completed a full run, did some testing while writing ofcourse. I shall make one this weekend when I'm finished on the tabs branch and adjusted the acceptance testing on the new functionality from there.

@FelixAkk FelixAkk reopened this Jun 8, 2012
@nielsAD
Collaborator
nielsAD commented Jun 8, 2012

I also propose letting other people test next week (Tristan / Alexey) as a form of acceptance testing.

@tvanhelden tvanhelden was assigned Jun 11, 2012
@tvanhelden

Proof read it and have some other people do testing. Apart from that its finished

@tvanhelden tvanhelden closed this Jun 18, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.