We are a small conference call company based out of Washington State. We have a new application that we have built that allows customers operate a conference call on our state of the art teleconferencing system. All they have to do is sign up, and when they do, the system will give them a free US based telephone number that people can call and conference with.
The only people who have used the system is the software engineers that wrote it. What needs to happen is we need a person who doesn't know the system to log in, become familiar with the system, and write documentation of how to use it for our users. It needs to be written in english. After you are done writing the documentation, we need you to test the software and draft up a list of procedures to actually test the software.
If we decide to work with you, you will work with the software engineers that wrote it. They will fully describe features to you if you have questions. They will work on Skype and email. There are two sets of documents we need. One for end users, and one for our test engineers.
What we need from you:
1. End user documentation written in english.
2. The documentation needs to be hosted in a documentation system of your recommendation. Maybe wordpress??? Maybe there is a better content management system. Just let us know. I'm not sure what is the best system.
3. We need test cases for how to test the software. This will be used by people who will be testing the software. We need a repeatable 'test script' that they operate for each new version of the software to make sure we didn't break anything. Here is a tiny list of test cases that I'd hope the technical writer would use and build from.
a. How to sign up, and when you sign up, where does the data go? How can we confirm that it was saved properly.
b. How to upgrade an account, where does the data go, how do we confirm it? What are the extra features that were activated and can we see them enabled?
c. How to create a conference, and test it in moderated and open mode. Confirming each step with multiple users in the conference.
d. Listening and checking for voice prompts in the conference. When should the user hear certain prompts, how do we test for it. Are the any prompts that are played based on several users logging in.
e. Can we log into different conferences at the same time, and make sure that the prompts are voices get played in their appropriate conferences?
f. How to test volume, recording, playback, upload and playback, which file formats work, etc.
g. What happens when paid for plan expires? How can we test that?
h. How do you add more numbers?
i. What if user wants to port their existing number?
j. Has the control panel been tested in IE, Safari, Chrome,Firefox? Are there others we should support?
k. How do we test each feature on the settings page.
***UPDATED BRIEF***
Test Case Developer
We are a small conference call company based out of Washington State. We have a new application that we have built that allows customers to create a conference call on our state of the art teleconferencing system. All they have to do is sign up, and when they do, the system will give them a free US based telephone number that people can call and conference with.
The system has a lot of features. They are attached to the document. The big features are:
Audio control of each user
A free/private telephone number for each conference. (PIN less conferences is the correct term)
Moderated (large conference) and Open (small conference) modes. An open conference is where everybody can just start talking all at once. A moderated conference is where everybody logs in muted. When they want to talk, they press a key on their phone to raise their hand, and the moderator allows them to speak.
Call Recording
Uploading audio files to play for all users to hear.
Extensive call management. (controlling every caller, blocking them, kicking them off, etc)
Security
The only people who have used the system is the software engineers that wrote it. What needs to happen is we need a person who doesn't know the system to log in, become familiar with the system, and write documentation of how to fully test all of the features. This test documentation will be given to several people who will test the system and report their bugs to the engineers.
If we decide to work with you, you will work with the software engineers that wrote it. They will fully describe features to you if you have questions. They will work on Skype and email. The primary engineer is in Dubai (UAE), and the project ‘owner’ is in Washington State (USA).
We need test cases for how to test the software. This will be used by people who will be testing the software. They will know how to log into the system, be able to access MySQL, and see the file system of the conference server. We need a repeatable 'test script' that they operate for each new version of the software to make sure we didn't break anything and that features operate properly. Each test case should include the steps to produce it, a method to verify that the expected behavior occurred, and that expected data was put in the appropriate places. You’ll have to log into MySQL, the Stripe backend, and be able to log into the servers to verify that files and settings are properly set.
Example Test Cases:
a. How to sign up, and when you sign up, where does the data go? How can we confirm that it was saved properly.
b. How to upgrade an account, where does the data go, how do we confirm it? What are the extra features that were activated and can we see them enabled?
c. How to create a conference, and test it in moderated and open mode. Confirming each step with multiple users in the conference.
d. Listening and checking for voice prompts in the conference. When should the user hear certain prompts, how do we test for it. Are the any prompts that are played based on several users logging in.
e. Can we log into different conferences at the same time, and make sure that the prompts are voices get played in their appropriate conferences?
f. How to test volume, recording, playback, upload and playback, which file formats work, etc.
g. What happens when paid for plan expires? How can we test that?
h. How do you add more numbers?
i. What if user wants to port their existing number?
j. Has the control panel been tested in IE, Safari, Chrome,Firefox? Are there others we should support?
k. How do we test each feature on the settings page.
We’d want you to develop 2 or 3 test cases, meet with the engineers to confirm that the test cases meet expectations, and then go ahead and develop test cases for each feature in the system, as well as some comprehensive test cases that test several of the features at a time as well as multiple users using the system.