TIMCAN Project, Functional Testing Plan

Hanna Alatalo
Jarkko Kuivanen
Elisa Nauha
Jere Ojala
Kimmo Urtamo

Version 1.0.0
Public
5.6.2019

University of Jyväskylä
Faculty of Information Technology

Abstract: The functional testing plan of TIMCAN project describes what functionalities are to be tested, how testing is executed and how the testing shall be reported.

Keywords: Test plan, functional testing, TIM, testing, The Centre for Applied Language Studies, adaptive feedback, dynamic feedback, virtual learning environment, plugin.

1. Target Application

The functionalities developed by TIMCAN project will replace already existing software called ICAnDoiT. ICAnDoiT is an application used by The Centre for Applied Language Studies for the purpose of studying adaptive feedback. Adaptive feedback is feedback that becomes gradually more detailed with every wrong response. The project team developed into the virtual learning environment called TIM a dropdown menu plugin, a drag-and-drop plugin, an adaptive feedback plugin and functionality for exporting the test results into a CSV file.

2. Target Features

Chapter describes the features developed in TIMCAN project that to be tested and the features which are excluded from testing.

2.1 Target Features

The target features are

• building a test,
• answering a test,
• exporting a report of the test,
• building a task with errors,
• a dropdown control,
• a radio selection and
• a drag-and-drop control.

2.2 Features Omitted from Testing

The features left outside of testing are

• test reporting from specified periods and
• validity filtering of the test reporting.

Date and time related features were omitted since they would require too much time between testing sessions. Dates and time commited to the database cannot be manually changed.

Filtering based on validity was omitted from the testing due to invalidating answers may not be possible within Feedback plugin.

3. Objectives of the Test Session and Methods of Execution

In the chapter the objectives and execution of the test session are described.

3.1 Objectives

In functional testing the most essential features are being tested with different inputs. The objective of this is to ensure that the system always functions in use the same way without errors.

3.2 Execution

Functional testing shall be executed as a black box testing manually. The testing data is choden using equivalence classes.

4. Test Run

Only the person who is executing the test shall participate in a test run. A tester should possess basic understanding of operating the Windows Operating System. The tester should also possess basic understanding of operating TIM system.

4.1 Testing Environment

For testing purpose a tester must have access to a computer with WWW browser and Internet connection.

4.2 Testing Report

The testing report should include from the test session its identification and summary.

The following information about the testing environment should be included to the testing session report:

• the software and version,
• the operating system and version,
• the browser and version,
• the working computer/device and version, and
• the test server of testing environment.

For identification of the testing session the following informations should be recorded:

• the name and version of the test plan,
• the test session participants,
• the test execution date and
• the tested test cases.

The summary should include

• the number of executed test cases,
• the number of test cases not executed,
• the number of each conclusion separately specified,
• exceptions from the test plan and their justifications and
• recommended procedures after the test session.

The conclusion of the test case must be one of the following:

• OK is the result when test case has succeeded with end result matching with the expected result.
• Error is the result when end result differs from the expected result or something generally harmful is noticed during the test run.
• Note is the result when the tester has noticed abnormality or suspicious in functionality.

In the case of Error and Note the observations should be reported with regarding details, such as procedures, input, abnormalities and possible error messages that led to the result.

The report of the test cases should be compiled on the following table form.

4.3 Identification of the Test Cases

The numbering of the test cases should be in form of [Case ID].[Subcase ID].

Case IDs by task titles are listed in the following table.

5. Test Cases for Building a Test

The test cases 1.1-1.4 tests successful building of the test with tasks.

5.1 Building a Test, Instruction Page

Test case: 1.1
Initial state: The user is signed in to TIM development machine.
Steps:

1. Create a new folder in your documents called TestausTesti1.
2. In Manage mode set Default rights for new documents in the folder to View for Logged-in Users.
3. In the folder create a document called TestInstructions.
4. Click Add Paragraph and copy the instructions markup (see Test data) and click Save.

Test data:

# Welcome to the test!

This is the instructions for the whole test. Please click below to begin test.

[Begin test](test1task1)

Expected result:

5.2 Building a Test, Task 1 with dropdown questions

Test case: 1.2
Initial state: The user is signed in to TIM development machine and has done the test case 1.1.
Steps:

1. Go to the folder TestausTesti1 in your documents.
2. In the folder create a document called test1task1.
3. Go to the Manage mode and copy the task markup from Appendix 1 into the Edit the full document box and click Save.
4. Go to the View mode.
5. In the View mode left click on the left side of the feedback paragraph and edit the paragraph.
6. Find the line nextTask: and write in "[Task 2](test1task2)".

Test data: See Appendix 1
Expected result: The task is ready and looks like so:

5.3 Building a Test, Task 2 with drag&drop questions

Test case: 1.3
Initial state: The user is signed in to TIM development machine and has excecuted the test case 1.2.
Steps:

1. Go to the folder TestausTesti1 in your documents.
2. In the folder create a document called Test1Task2.
3. Go to the Manage mode and copy the task markup from Appendix 2 into the Edit the full document box and click Save.
4. Go to the View mode.
5. In the View mode left click on the left side of the feedback paragraph and edit the paragraph.
6. Find the line nextTask: and write in "[End of test](endoftest)".

Test data: See Appendix 2.
Expected result: The task is ready and looks like so:

5.4 Building a Test, End Page of Test

Test case: 1.4
Initial State: The test cases 1.1-1.3 have been completed successfully
Steps:

1. Go to the folder.
2. Create new document called EndOfTest.
3. Add a paragraph with the test data.
4. Go to View mode.

Test Data:

# Thank you for taking part in the test!

Expected Result:

In View mode the page should look like below:

The test folder should look like below:

6. Test Cases for Student Answering the Test

Test case 2.1-2.4 tests successful answering to the test created in the test cases 1.1-1.4 as a student.

6.1 Beginning a Test as Student

Test case: 2.1
Initial State: The test has been successfully built in the test cases 1.1-1.4.
Steps:

1. Sign in to TIM as the test user with the username test1@example.com and the password test1.
2. Go to the page of the test https://timdevs01-2.it.jyu.fi/view/users/*username*/testaustesti1/testinstructions.

Test Data:
Expected Result: The instruction page for the test is visible.

6.2 Answering the Task until Stopping Condition for Correct Streak is Reached

Test case: 2.2
Initial State: The test cases 2.1 has been successfully completed.
Steps:

Test Data: See individual steps for data.
Expected Result: See the image below and the individual steps for expected results.

6.3 Answering the Task Until Stopping Condition for Final Feedback Level is Reached

Test case: 2.3
Initial State: The test cases 2.1-2.2 have been successfully completed.
Steps:

Test Data: Wrong answers for the questions in task 2 include

• if run I a mile,
• who at work I see,
• had whether I a computer, and
• when come I around.

Expected Result: See image below and the individual steps for expected results.

6.4 Answering the Test and Not Choosing Options

Test case: 2.4
Initial State: The test cases 2.1-2.3 have been successfully completed.
Steps:

Test Data: The right answers for the questions in task 2 are

• if I run a mile,
• who I see at work,
• whether I had a computer, and
• when I come around.
  

Expected Result: See the individual steps for expected results.

7. Test Cases for Report Exporting

The test cases 3.1-3.13 tests successful exporting of the test results with various options.

7.1 Template for Test Cases 3.1-3.7

The test cases 3.1-3.7 all follow this template but with individual test data and final expected results.

Test cases: 3.1-3.7
Initial State: The test cases 1.1-2.4 have been successfully completed.
Steps:

7.2 Exporting Test Results with Default Options

Test case: 3.1
Initial State: See Template for test cases 3.1-3.7.
Steps: See Template for test cases 3.1-3.7.

Test Data:

Export Options:
Period: Whenever
Validity: Valid
Names: Username and fullname
Scope: Only this task
Answers From: All users
Delimiter: Semicolon
Decimal: Decimal point

Expected Result:
The report should only include answers from test1task1 document. The names should include both the username and the full name. The headers should include both the username and the full name. The delimiters should be separated with semicolon. The time should be displayed with decimal point.

7.3 Exporting Results of the Whole Test and with Only Username

Test case: 3.2
Initial State: See Template for test cases 3.1-3.7.
Steps: See Template for test cases 3.1-3.7.

Test Data:

Export Options:
Period: Whenever
Validity: Valid
Names: Username only
Scope: The whole test
Answers From: All users
Delimiter: Semicolon
Decimal: Decimal point

Expected Result:

The report should include answers from the whole test folder. The full name should be not displayed neither the respectful header.

7.4 Exporting Results of the Whole Test and with Anonymous Username

Test case: 3.3
Initial State: See Template for test cases 3.1-3.7.
Steps: See Template for test cases 3.1-3.7.

Test Data:

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers from: All users
Delimiter: Semicolon
Decimal: Decimal point

Expected Result:

The report should include answers from the whole test folder. At the header the username should display users anonymously, as in user1 and user2.

7.5 Exporting Test Results with Tab-Delimiters

Test case: 3.4
Initial State: See Template for test cases 3.1-3.7.
Steps: See Template for test cases 3.1-3.7.

Test Data:

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: All users
Delimiter: Tab
Decimal: Decimal point

Expected Result:

The report should include answers from the whole test folder. The delimiters should be tabulators. Only anonymous username is displayed.

7.6 Exporting Test Results with Vertical Bar-Delimiters

Test case: 3.5
Initial State: See Template for test cases 3.1-3.7.
Steps: See Template for test cases 3.1-3.7.

Test Data:

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: All users
Delimiter: Vertical bar
Decimal: Decimal point

Expected Result:

The report should include answers from the whole test folder. The delimiters should be vertical bars. Only username is displayed in headers.

7.7 Exporting Test Results with Comma-Delimiters

Test case: 3.6
Initial State: See Template for test cases 3.1-3.7.
Steps: See Template for test cases 3.1-3.7.

Test Data:

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: All users
Delimiter: Comma
Decimal: Decimal point

Expected Result:

The report should include answers from the whole test folder. The delimiters should be commas. Only the username is displayed.

7.8 Exporting Test Results with Decimal Comma

Test case: 3.7
Initial State: See Template for test cases 3.1-3.7.
Steps: See Template for test cases 3.1-3.7.

Test Data:

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: All users
Delimiter: Comma
Decimal: Decimal comma

Expected Result:

The report should include answers from the whole test folder. The time should be displayed with decimal commas with quotation marks. Only the username is displayed.

7.9 Template for Test Cases 3.8-3.12

The test cases 3.8-3.12 all follow this template but with individual test data and final expected results.

Test cases: 3.8-3.12
Initial State: The test cases 1.1-2.4 have been successfully completed.
Steps:

7.10 Exporting Test Results with Only One Visible User

Test case: 3.8
Initial State: See Template for test cases 3.8-3.12.
Steps: See Template for test cases 3.8-3.12.

Test Data:

Step 4: Enter the text field Full Name and input user 1.

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: Only visible users
Delimiter: Comma
Decimal: Decimal comma

Expected Result:

Step 4: The user list should only display Test user 1.

Final Result: The report should include answers from the whole test folder. The report should only include answers from Test user 1.

7.11 Exporting Test Results with Two Visible Users

Test case: 3.9
Initial State: See Template for test cases 3.8-3.12.
Steps: See Template for test cases 3.8-3.12.

Test Data:

Step 4: Enter the text field Full Name and input test.

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: Only visible users
Delimiter: Comma
Decimal: Decimal comma

Expected Result:

Step 4: The user list should both display Test user 1 and Test user 2

Final result:

The report should include answers from the whole test folder. The report should include answers from both Test user 1 and Test user 2.

7.12 Exporting Test Results with Only Visible Users when Visible User List is Empty

Test case: 3.10
Initial State: See Template for test cases 3.8-3.12.
Steps: See Template for test cases 3.8-3.12.

Test Data:

Step 4: Enter the text field Full Name and input k

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: Only visible users
Delimiter: Comma
Decimal: Decimal comma

Expected Result:

Step 4: The user list should be empty.

Final result: The report should only include row of headers and no user data. Full Name header should not be included.

7.13 Exporting Test Results with Only Selected User

Test case: 3.11
Initial State: See Template for test cases 3.8-3.12.
Steps: See Template for test cases 3.8-3.12.

Test Data:

Step 4: Select Test user 2 from the user list.

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: Only selected user
Delimiter: Comma
Decimal: Decimal comma

Expected Result:

Step 4: The user list should have Test user 2 highlighted.

Final Result: The report should include answers from the whole test folder. The report only include answers from Test user 2.

7.14 Exporting Test Results with Only Selected User when Visible User List is Empty

Test case: 3.12
Initial State: See Template for test cases 3.8-3.12.
Steps: See Template for test cases 3.8-3.12.

Test Data:

Step 4.1: Select Test user 2 from user list.
Step 4.2: Enter the text field Full Name and type foobar.

Export Options:
Period: Whenever
Validity: Valid
Names: Anonymous username
Scope: The whole test
Answers From: Only selected user
Delimiter: Comma
Decimal: Decimal comma

Expected Result:

Step 4.1: The user list should have Test user 2 highlighted.
Step 4.2: The user list should be empty.

Final Result: The report should only include row of headers and no user data. Full Name header should not be included.

7.15 Canceling Exporting

Test case: 3.13
Initial State: Test cases 1.1-2.4 have been successfully completed.
Steps:

Expected Result: See individual steps for expected results.

8. Building Task with Errors

The test cases 4.1-4.7 tests error handling of the test creation.

8.1 Building Task with Varying Number of Feedback Levels

Test case: 4.1
Initial State: A folder called TestausTesti1 has been created.
Steps:

1. Go to folder TestausTesti1 in your documents.
2. In the folder create a document called Test1Task3.
3. Go to the Manage mode and copy the task markup from Appendix 1 into the Edit the full document box and click Save.
4. Go to View mode and click to edit the feedback paragraph.
5. Delete a feedback level from one match option such as:
   - "Level 2 feedback: You answered: *|answer|* Answer is wrong. Try thinking *a bit* harder. "
6. Click Save. The expected result is the appearance of a red warning: Different number of feedback levels.
7. Go to View mode and click to edit the feedback paragraph.
8. Paste the deleted feedback level back in the right place.
9. Click Save. Expected result is that error disappears.

Test Data: See individual steps for data.
Expected Result: In step 6 an error should appear and be recovered from in step 9.

8.2 Building Task with No Link to Next Task or End of Test

Test case: 4.2
Initial State: An errorless task Test1Task3 has been created (test case 4.1).
Steps:

1. Click to edit the feedback paragraph of document Test1Task3.
2. Delete the input of nextTask
3. Click Save. The expected result is the appearance of a red warning The following fields have invalid values: nextTask: Field may not be null.
4. Click to edit the feedback paragraph.
5. Reinput "link" into the nextTask field.
6. Click Save. The expected result is that error should disappear.

Test Data: See individual steps for data.
Expected Result: In step 3 an error should be displayed and it should be recovered from in step 6.

8.3 Building Task with No Instruction Block Defined

Test case: 4.3
Initial State: An errorless task Test1Task3 has been created (test case 4.1).
Steps:

1. Click to edit the instructions paragraph of document Test1Task3.
2. Delete the instruction paragraph ID .instruction and click Save.
3. Click to edit the feedback paragraph and click Save. The expected result is the appearance of a red warning Instruction not defined.
4. Click to edit the instructions paragraph.
5. Reinput the instruction plugin and click Save.
6. Click to edit the feedback paragraph and click Save. The expected result is that the error should disappear.

Test Data: See individual steps for data.
Expected Result: In step 3 an error should be displayed and it should be recovered from in step 6.

8.4 Building Task with No Right Answer Defined

Test case: 4.4
Initial State: An errorless task Test1Task3 has been created (test case 4.1).
Steps:

1. Click to edit the feedback paragraph of document Test1Task3.
2. Delete the lines:
   

    - match: [is baking]
      correct: true
      levels: *ismatch

3. Click Save. The expected result is the appearance of a red warning No correct answer defined for question item..
4. Click to edit the feedback paragraph.
5. Reinput the deleted text.
6. Click Save. the expected result is that the error should disappear.

Test Data: See individual steps for data.
Expected Result: In step 3 an error should be displayed and it should be recovered from in step 6.

8.5 Building Task with Wrong Names for Plugins

Test case: 4.5
Initial State: An errorless task Test1Task3 has been created (test case 4.1).
Steps:

1. Click to edit the feedback paragraph of document Test1Task3.
2. Change the pluginname drop1 on line 7 to nodrop1.
3. Click Save. The expected result is the appearance of a red warning No plugin with such a name (nodrop1) or missing setPluginWords-method.
4. Click to edit the feedback paragraph.
5. Change the pluginname nodrop1 on line 7 back to drop1.
6. Click Save. The expected result is that the error should disappear.

Test Data: See individual steps for data.
Expected Result: In step 3 an error should be displayed and it should be recovered from in step 6.

8.6 Building Task with No Default Feedback

Test case: 4.6
Initial State: An errorless task Test1Task3 has been created (test case 4.1).
Steps:

1. Click to edit the feedback paragraph of document Test1Task3.
2. Delete lines:

    - match: []
      levels: *defaultmatch

3. Click Save. The expected result is the appearance of a red warning: Default feedback option needed.
4. Click to edit the feedback paragraph.
5. Reinput the deleted text.
6. Click Save. the expected result is that the error should disappear.

Test Data: See individual steps for data.
Expected Result: In step 3 an error should be displayed and it should be recovered from in step 6.

8.7 Building Task with No Feedback

Test case: 4.7
Initial State: An errorless task Test1Task3 has been created (test case 4.1).
Steps:

1. Click to edit the feedback paragraph of document Test1Task3.
2. Delete lines:

  choices:
    - match: [is baking]
      correct: true
      levels: *ismatch
    - match: [do baking]
      levels: *domatch
    - match: [are baking]
      levels: *arematch
    - match: []
      levels: *defaultmatch

3. Click Save. The expected result is a YAML error.
4. Click to edit the feedback paragraph.
5. Reinput the deleted text.
6. Click Save. The expected result is that a YAML error should disappear.

Test Data: See individual steps for data.
Expected Result: In step 3 an error should be displayed and it should be recovered from in step 6.

``` {settings=""}
hide_links: view
hide_top_buttons: view

css: |!! 
.paragraphs {
display: none;
} 
!!
```

#- {area="dropdowntask1" .task}

## Instructions {.instruction defaultplugin="dropdown"}

Welcome to the test. Read the question carefully.
If you get the answer wrong, please read the feedback carefully.


Please try out a practice question:


I {#practice words: [will think, won't think, might think]} before answering.


## Item: {defaultplugin="dropdown"}

What {#dropdown1} on the stove?


## Item: {defaultplugin="dropdown"}

Who {#dropdown2} the cake?


## Item: {defaultplugin="dropdown"}

What {#dropdown3} on the roof?


## Item: {defaultplugin="dropdown"}

Who {#dropdown4} the 3 mile swim in the race?
 

``` {#fb1 plugin="feedback"}
correctStreak: 2
nextTask: nonexttaskdefined
questionItems:
- pluginNames: [dropdown1]
  words: [[is cooking, do cooking, are cooking]]
  choices:
    - match: [is cooking]
      correct: true
      levels: &ismatch
        - "**Correct!** You answered: |answer|"
    - match: [do cooking]
      levels: &domatch
        - "Level 1 feedback: You answered: *|answer|* Answer is wrong.
        - Try **thinking**. "
        - "Level 2 feedback: You answered: *|answer|* Answer is wrong.
        - Try thinking *a bit* harder. "
        - "Level 3 feedback: You answered: *|answer|* Answer is wrong.
        - Try thinking **much more** harder. "
        - "Level 4 feedback: You answered: *|answer|* Answer is wrong.
        - Just think about what the answer **is**. "
        - "Level 5 feedback: Please note the correct answer: 'What **is** / Who **is**'"
    - match: [are cooking]
      levels: &arematch
        - "Level 1 feedback: You answered: *|answer|* Answer is wrong.
        - Try **thinking**. "
        - "Level 2 feedback: You answered: *|answer|* Answer is wrong.
        - Try thinking *a bit* harder. "
        - "Level 3 feedback: You answered: *|answer|* Answer is wrong.
        - Try thinking **much more** harder. "
        - "Level 4 feedback: You answered: *|answer|* Answer is wrong.
        - Just think about what the answer **is**. "
        - "Level 5 feedback: Please note the correct answer: 'What **is** / Who **is**'"
    - match: []
      levels: &defaultmatch
        - "Level 1 feedback: default feedback for drop4"
        - "Level 2 feedback: default feedback for drop4"
        - "Level 3 feedback: default feedback for drop4"
        - "Level 4 feedback: default feedback for drop4"
        - "Level 5 feedback: Please note the correct answer: 'What **is** / Who **is**'"
- pluginNames: [dropdown2]
  words: [[is baking, do baking, are baking]]
  choices:
    - match: [is baking]
      correct: true
      levels: *ismatch
    - match: [do baking]
      levels: *domatch
    - match: [are baking]
      levels: *arematch
    - match: []
      levels: *defaultmatch
- pluginNames: [dropdown3]
  words: [[is jumping, do jumping, are jumping]]
  choices:
    - match: [is jumping]
      correct: true
      levels: *ismatch
    - match: [do jumping]
      levels: *domatch
    - match: [are jumping]
      levels: *arematch
    - match: []
      levels: *defaultmatch
- pluginNames: [dropdown4]
  words: [[is swimming, do swimming, are swimming]]
  choices:
    - match: [is swimming]
      correct: true
      levels: *ismatch
    - match: [do swimming]
      levels: *domatch
    - match: [are swimming]
      levels: *arematch
    - match: []
      levels: *defaultmatch
```
#- {area_end="dropdowntask1"}

``` {settings=""}
hide_links: view
hide_top_buttons: view

css: |!! 
.paragraphs {
display: none;
} 
!!
```

#- {area="dragtask1" .task}

## Instructions {.instruction defaultplugin="drag"}

Welcome to the test. Read the question carefully.
If you get the answer wrong, please read the feedback carefully.


Please try out a practice question:

Order the words correctly into the sentence below.

Drag from here: {#practice1 words: [I, before, will think, answering]}


To here: {#practice2}.


## Item {defaultplugin="drag"}
::: {.info}
Please order the words correctly into the sentence below.


{#drag1 words: [I, when, around, come]}

:::
You know where I'll be found {#drop1}.


## Item {defaultplugin="drag"}
::: {.info}
Please order the words correctly into the sentence below.


{#drag2 words: [I, if, a mile, run]}

:::
I will be quite tired {#drop2}.


## Item {defaultplugin="drag"}
::: {.info}
Please order the words correctly into the sentence below.


{#drag3 words: [I, who, at work, see]}

:::
I will tell you {#drop3}.


## Item {defaultplugin="drag"}
::: {.info}
Please order the words correctly into the sentence below.


{#drag4 words: [I, whether, a computer, had]}

:::
He wanted to know {#drop4}.



``` {#fb1 plugin="feedback"}

correctStreak: 2
nextTask: nonexttaskdefined
questionItems:
- pluginNames: [drop1]
  dragSource: drag1
  words: []
  choices:
    - match: [when I come around]
      correct: true
      levels: &rightmatch
        - "**Correct!** You answered: |answer|"
    - match: [when around I come]
      levels: &asvmatch
        - "Level 1 feedback: You answered: *|answer|* Answer is wrong.
        - Try **thinking**. "
        - "Level 2 feedback: You answered: *|answer|* Answer is wrong.
        - Try thinking *a bit* harder. "
        - "Level 3 feedback: You answered: *|answer|* Answer is wrong.
        - Try thinking **much more** harder. "
        - "Level 4 feedback: You answered: *|answer|* Answer is wrong.
        - Just think about **what the answer is**. "
        - "Level 5 feedback: Please note the correct word order:
        - 'conjuction subject verb the rest'"
    - match: [when come I around]
      levels: &vsamatch
        - "Level 1 feedback: You answered: *|answer|* Answer is wrong.
        - Try **thinking**. "
        - "Level 2 feedback: You answered: *|answer|* Answer is wrong.
        - Try thinking *a bit* harder. "
        - "Level 3 feedback: You answered: *|answer|* Answer is wrong.
        - Try thinking **much more** harder. "
        - "Level 4 feedback: You answered: *|answer|* Answer is wrong.
        - Just think about **what the answer is** "
        - "Level 5 feedback: Please note the correct word order:
        - 'conjuction subject verb the rest'"
    - match: []
      levels: &defaultmatch
        - "Level 1 feedback: You answered: *|answer|* Answer is wrong.
        - Try **thinking**."
        - "Level 2 feedback: You answered: *|answer|* Answer is wrong.
        - Think about what comes first."
        - "Level 3 feedback: You answered: *|answer|* Answer is wrong.
        - Think about what word comes first."
        - "Level 4 feedback: You answered: *|answer|* Answer is wrong.
        - The conjunction should come first."
        - "Level 5 feedback: Please note the correct word order:
        - 'conjuction subject verb the rest'"
- pluginNames: [drop2]
  dragSource: drag2
  words: []
  choices:
    - match: [if I run a mile]
      correct: true
      levels: *rightmatch
    - match: [if a mile I run]
      levels: *asvmatch
    - match: [if run I a mile]
      levels: *vsamatch
    - match: []
      levels: *defaultmatch
- pluginNames: [drop3]
  dragSource: drag3
  words: []
  choices:
    - match: [who I see at work]
      correct: true
      levels: *rightmatch
    - match: [who at work I see]
      levels: *asvmatch
    - match: [who see I at work]
      levels: *vsamatch
    - match: []
      levels: *defaultmatch
- pluginNames: [drop4]
  dragSource: drag4
  words: []
  choices:
    - match: [whether I had a computer]
      correct: true
      levels: *rightmatch
    - match: [whether a computer I had]
      levels: *asvmatch
    - match: [whether had I a computer]
      levels: *vsamatch
    - match: []
      levels: *defaultmatch

```
#- {area_end="dragtask1"}