<commit_before><!-- @@author A0139661Y -->

# Test Instructions

Welcome, tester. We are happy to have you on board the CMDo team. Here are some instructions to get you started.

## Setup
1) Download `[F11-C2][CMDo-v0.5].jar` from the Releases page.
2) On first run, the folder `data` is created where the JAR file is run. It contains storage file `cmdo.xml`. This is the default storage file name. All storage files must have this name. You are free to rename the folder `data` to whatever you want, see step 7 for more)
3) Quit the application by typing in `exit` and delete `cmdo.xml`.
4) Download `SampleData.xml` from the directory `\src\test\data\ManualTesting\` into `data`.
5) Rename `SampleData.xml` to `cmdo.xml`.
6) Run the application. You are now ready to begin testing!
7) _Optional:_ If you decide to change the name of the folder `data`, to, say `DropBox`, you must also let CMDo know. In `CMDo`, type in 
    ```
    storage DropBox
    ```
    You would have tested our [storage change functionality](###Change-Storage) already. Well done!

## Sample Codes

CMDo hosts a couple of interesting features that we need you to help test.

We have provided some sample test cases which you can start with. The input and expected output at the result display box below the command box are provided for your reference.

We recommend that you perform the tests in the order listed so that we fit in our assumptions well. (i.e. `delete 1` when there is nothing at index 1 returns a different outcome) If you do so, set your system time and date to **Nov 5, 2016, 9pm.**

#### _**!! Please note that CMDo runs on date input format MM/DD/YYYY !!**_

### Add
Adds a new task. Tasks have 
- 'details'
- date and time (both, either, or none; start and/or end)
- priority levels `HIGH, MEDIUM, LOW, or NONE`
- multiple [tags]
```
add new task                         # "Encapsulate your details in ' '"
add ``                               # "Blank task? Did you mean to block out a date? Type help to see usage."
add 'hershey's hersh'                # Adds a task 'hershey's hersh'
add 'date' 10/31/2016                # Adds a task 'date' due on 10/31/2016
add 'time' 1300                      # Adds a task 'time' due today at 1pm
add 'range' tmr 1300 to 12/31 1400   # Adds a task 'range' from tomorrow 1pm to 12/31 2pm
add 1300 '5pm' /high                 # Adds a task '5pm' due today at 1pm with priority HIGH
add 'tag' -tag1 -tag2                # Adds a task 'tag' with tags tag1 and tag2<commit_msg>Fixed number bullet formatting.<commit_after><!-- @@author A0139661Y -->

# Test Instructions

Welcome, tester. We are happy to have you on board the CMDo team. Here are some instructions to get you started.

## Setup
1. Download `[F11-C2][CMDo-v0.5].jar` from the Releases page.
2. On first run, the folder `data` is created where the JAR file is run. It contains storage file `cmdo.xml`. This is the default storage file name. All storage files must have this name. You are free to rename the folder `data` to whatever you want, see step 7 for more)
3. Quit the application by typing in `exit` and delete `cmdo.xml`.
4. Download `SampleData.xml` from the directory `\src\test\data\ManualTesting\` into `data`.
5. Rename `SampleData.xml` to `cmdo.xml`.
6. Run the application. You are now ready to begin testing!
7. _Optional:_ If you decide to change the name of the folder `data`, to, say `DropBox`, you must also let CMDo know. In `CMDo`, type in 
    ```
    storage DropBox
    ```
    You would have tested our [storage change functionality](###Change-Storage) already. Well done!

## Sample Codes

CMDo hosts a couple of interesting features that we need you to help test.

We have provided some sample test cases which you can start with. The input and expected output at the result display box below the command box are provided for your reference.

We recommend that you perform the tests in the order listed so that we fit in our assumptions well. (i.e. `delete 1` when there is nothing at index 1 returns a different outcome) If you do so, set your system time and date to **Nov 5, 2016, 9pm.**

#### _**!! Please note that CMDo runs on date input format MM/DD/YYYY !!**_

### Add
Adds a new task. Tasks have 
- 'details'
- date and time (both, either, or none; start and/or end)
- priority levels `HIGH, MEDIUM, LOW, or NONE`
- multiple [tags]
```
add new task                         # "Encapsulate your details in ' '"
add ``                               # "Blank task? Did you mean to block out a date? Type help to see usage."
add 'hershey's hersh'                # Adds a task 'hershey's hersh'
add 'date' 10/31/2016                # Adds a task 'date' due on 10/31/2016
add 'time' 1300                      # Adds a task 'time' due today at 1pm
add 'range' tmr 1300 to 12/31 1400   # Adds a task 'range' from tomorrow 1pm to 12/31 2pm
add 1300 '5pm' /high                 # Adds a task '5pm' due today at 1pm with priority HIGH
add 'tag' -tag1 -tag2                # Adds a task 'tag' with tags tag1 and tag2
{'fraction_non_alphanumeric': 0.0878968253968254, 'fraction_numerical': 0.030952380952380953, 'mean_word_length': 2.9199066874027992, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 10}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 6, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5888495', 'n_tokens_mistral': 1595, 'n_tokens_neox': 1441, 'n_words': 780}