URL: http://www.uburst.com/cgi-bin/dcforum/dcboard.cgi
Forum: uReserve_general
Thread Number: 12
[ Go back to previous page ]

Original Message
"4 (hopefully simple) questions"

Posted by richardpoteat [rpoteat@onebox.com] on at 10:38 PM
i am currently evaluating the trial version of utest, and have come up with 4 questions, which i will list below:

1). How can you do a word wrap in an answer applet? i have several questions with 20+ words as each answer. currently, utest simply cuts off the words that will not fit, and puts the rest on the next line next to a new checkbox. this doesn't work, as the new line is a continuation of the old line.

2) are there any special setup instructions for creating webpages using frontpage 2000 (or 2002)? i have tried copy and paste in the text window, but every time i switch to preview mode, (even by saving it and launching ie), i only see the code, not the expected result. can anyone help with this?

3) how do you put in answers on the answer key applet? i've read the instructions, but i'm still confused on this one...

4) is there a configurable countdown clock feature that will automatically stop the test when time runs out available?

i hope you can help me with this.
thanks in advance,
richard poteat

Table of contents

Messages in this discussion
"4 (hopefully useful) answers"
Posted by Joseph Pishgar [support@uburst.com] on at 02:41 PM
1. As for wrapping text in an applet, this can be a little tricky and isn't really recommended. Bigger applets take longer to load, most of the uTest ones are designed for short answers to appear next to them, a short description of sorts, while the HTML that appears near the applet's answer elaborate on what the answers mean. For instance, an applet might have an answer that just has the letter A. as text within the applet, but outside the applet the A. is the A. answer described. Sticking the text in the HTML next to the applet is the better way to go.

2. Frontpage and other WYSIWYG editors have a tendancy to, if you aren't careful, mangle code. The best thing to do is to use a text editor like NotePad or WordPad to do your HTMLing.

3. All you need to do is to specify whether or not to show the answers in the uTestFinishButton1 applet with the parameters.

<PARAM NAME="answer_key" VALUE="example_answers.txt">
<PARAM NAME="show_answer" VALUE="YES">

4. Currently, there is no way to "stop" a test from continuing when the clock reaches a certain time... but something similar to that has been suggested before, and is considered on uTest's future feature wishlist.

Hope this helps.

Joseph Pishgar
Microburst Technologies, Inc.

"RE: 4 (hopefully simple) questions"
Posted by Bill Weiner on at 06:58 AM
Richard, here is some additional info:

1) Remember that you can put all of the information on the page using regular HTML.. and then just use the uTest applets as the means for allowing customers to choose their answer.

For instance, using regular HTML, you could put the entire question on the page... and also using regular HTML, you could put the entire answers/options on the page. Then the uTest Answer applet could be used to just prompt the customer to "Select Your Answer:" and only the letters (A, B, C or D) in the applet that correspond to the full HTML answers.

2) Unfortunately, I'm not that familiar with using the frontpage HTML editor... but I know people do us it with uTest. Maybe there is some configuration option relating to Java Applets?

3) Yes, the uTestFinishButton applets allow you to specify the name of the answer key file, such as:

< PARAM NAME="answer_key" VALUE="example_answers.txt" >

In this file, you then just specify the question numbers/answers in the format question#=answer, such as:

3=President Bush


See the "example_answers.txt" file that comes with uTest (in the classes directory) as an example.

4) There is a uTestClock applet that displays the current running test time... but there is no built-in option at this time that would force the student to end the test.

Now as a work-around, you could write your own JavaScript that utilizes the "getTestTime()" method (as described in the uTest Programmer's Guide: http://www.uburst.com/uTest/reference/programmers_guide.html ) ... but that still won't be fool-proof because there would be nothing to prevent the student from just quitting the test and starting over until they finish the test quick enough.