![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
As most of you who read this know, I am a software developer. As you also know, I am in my final semester of school, and am working to create a program for use designing the curriculum for a martial arts school.
Part of the formal process of software development includes testing by people other than the developer(s). This is typically done in three stages: Alpha testing, Beta testing, and QA testing.
As used here, Alpha testing is the early testing of individual pieces to confirm that they function as expected. Beta testing is looking over the proposed finished product as a whole, confirming that all pieces function as expected. QA testing is looking over everything and trying to find ways to break it. ::G::
I currently have one person who has volunteered for Alpha-only testing, one for Beta-only testing, one for both Alpha and Beta (requires separate machines), and one for QA testing. This is enough to get by, but more would be welcomed.
Here is what would be involved for each role:
Alpha tester -- I will send you an executable program and one or more test plans. You run the program, go through the test plan, and send me your results and feedback. Time frame: October 15 - November 4.
QA tester -- I will send you an executable program and documentation. You read through the documentation (and suggest any edits), run the program, and see if there is anything you can do to cause the program to crash or otherwise malfunction. Time frame: November 5 - November 11.
Beta tester -- I will send you an executable program, documentation, and a set of test plans. You read the documentation (and suggest any edits), run the program, go through the test plans, and send me your results and feedback. Time frame: November 12 - November 18.
If you feel like volunteering for any or all of the roles above, please let me know! Once I've gotten a look at how many people are volunteering for which roles, I'll get back with you with confirmation and further details.
Thank you!!!
Part of the formal process of software development includes testing by people other than the developer(s). This is typically done in three stages: Alpha testing, Beta testing, and QA testing.
As used here, Alpha testing is the early testing of individual pieces to confirm that they function as expected. Beta testing is looking over the proposed finished product as a whole, confirming that all pieces function as expected. QA testing is looking over everything and trying to find ways to break it. ::G::
I currently have one person who has volunteered for Alpha-only testing, one for Beta-only testing, one for both Alpha and Beta (requires separate machines), and one for QA testing. This is enough to get by, but more would be welcomed.
Here is what would be involved for each role:
Alpha tester -- I will send you an executable program and one or more test plans. You run the program, go through the test plan, and send me your results and feedback. Time frame: October 15 - November 4.
QA tester -- I will send you an executable program and documentation. You read through the documentation (and suggest any edits), run the program, and see if there is anything you can do to cause the program to crash or otherwise malfunction. Time frame: November 5 - November 11.
Beta tester -- I will send you an executable program, documentation, and a set of test plans. You read the documentation (and suggest any edits), run the program, go through the test plans, and send me your results and feedback. Time frame: November 12 - November 18.
If you feel like volunteering for any or all of the roles above, please let me know! Once I've gotten a look at how many people are volunteering for which roles, I'll get back with you with confirmation and further details.
Thank you!!!
Tags:
no subject
And yes, it would be *additional* help, as I've already got one of our QA folks here at work who's agreed to do it as well.
As for time, I'm thinking probably 30 minutes, maybe an hour? What I'm planning on doing is giving you something showing you how it *should* be done (5-10 minutes), then let you work from there to see if you can break it ::G::, then send me feedback on what you tried and what the results were (i.e. "worked" or "caused error _______").