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

Original Message
"Additional test types"

Posted by Greg Henderson [gregh_oh@hotmail.com] on at 05:39 PM
I'm evaluating uTest for our company and so far am very pleased with what I'm seeing.

We are single-sourcing between print and HTML and would like to be able to have all our question types supported in both media. In our print documents, we support the following test types:

1) True/False
2) Long Answer
3) Short answer (fill-in)
4) Multiple choice
5) Multiple answer
6) Matching
7) Prioritization

The first five are handled nicely by the applets, but the other two appear to have no counterparts.
For clarity, Matching would be:
Question 1)
Match the following terms with their definitions.

A. term1 __ Definition 1
B. term2 __ Definition 2
C. term3 __ Definition 3
D. term4
etc

Prioritization would be:
Question 2)
Number the steps of the following process in their order of completion:
__ Step 1 description
__ Step 2 description
__ Step 3 description
__ Step 4 description
etc.

It is possible to implement each part of a matching or prioritization as an individual question, but there doesn't appear to be a way to have a single question consist of the multiple parts.

You have done something similar with uTestAnswer10.class where multiple images are part of a single question, so I was wondering if the same is possible for these two additional types.
Each could be accomlished by using the same pick-list of numbers (prioritization) or letters (matching) for each component. The tricky part would be to get the individual parts to be scored as a single question.

Thanks,
Greg


Table of contents

Messages in this discussion
"RE: Additional test types"
Posted by Bill Weiner on at 06:07 AM
Yes, both "matching" and "prioritization" question types can be handled. See pages 3 and 4 of the following demo as an example:

http://www.uburst.com/uTest/demo/geography.html

Those do require each option to be treated as a separate question... but you can change the "points" of each question such that they add up to the desired question weight.

Otherwise, there is always the option of using regular HTML to create your own < FORM > with the desired "matching" or "prioritization" options. The uTest JavaScript API could then be used to take the data from your < FORM > and save it on the answer sheet as 1 single question.


"RE:Additional test types"
Posted by Greg Henderson [gregh_oh@hotmail.com] on at 08:56 PM
OK, I see now how prioritization and matching questions can be built.

Now for today's related issue:
In order to have prioritization questions and matching questions not mess up the test numbering, I am thinking of creating an algorythm to move the answers to higher numbers outside of the range of question numbers.

For example, if Question 4 is a matching question with 5 parts, instead of assigning the answers to positions 5-10 of the answer sheet, the algorythm will assign them to questions 141-145 and enter them on the answer sheet as such.

My questions are:

1) Can the answer sheet have gaps, or must the numbers be contiguous (and present)? e.g.
1=
2=
3=
4=
7=
8=
9=
10=
141=
142=
etc.

2) Do the numbers have to be in order? i.e. is this ok:

1=
5=
3=
7=
141=
9=
etc.

Will either of these impact the scoring or any other aspect of usage.

Thanks,
Greg


"RE:Additional test types"
Posted by Greg Henderson [gregh_oh@hotmail.com] on at 09:57 PM
As a followup, can the answer key have non-numeric entries? for example:
1=
2=
3a=
3b=
3c=
3d=
4=
5=
etc.

Again, I'm trying to accomodate those priority and matching questions.

Thanks,
Greg


"RE:Additional test types"
Posted by Bill Weiner on at 06:40 AM
In regard to having non-numeric question numbers.... Unfortunately, No. At this time, all question numbers must be integers.

"RE:Additional test types"
Posted by Bill Weiner on at 06:37 AM
The algorithm that is used to dynamically create the HTML for the answer sheet will automatically display the answers in increasing numeric order. Such as:

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

If any numbers in the test are skipped (ie. by the user not answering a question or by simply not having an applet for a question), then those answers will simply be left blank on the answer sheet. For instance, if a 10 question test doesn't have an applet for question #8, then the answer sheet will still be displayed as:

1. A
2. B
3. C
4. D
5. A
6. B
7. C
8.
9. A
10. B

Note that the order in which the applets are placed on the test HTML pages... and the order in which the user answers the questions... does not affect the display of the answers on the answer sheet. They'll always be displayed in increasing numeric order.

The only exception to the above rule is that Long Answer and Essay questions will always be displayed at the bottom of the answer sheet. That is, suppose a test has this sort of question types:

Questions 1 - 5 are multiple choice
Question 6 is a long answer type
Question 7 and 8 are true/false
Question 9 is an essay type
Question 10 is a short answer type

The answers would then be displayed on the answer sheet with the "Long Answer" and "Essay" questions at the bottom:

1.
2.
3.
4.
5.
7.
8.
10.
---
6.
---
9.