Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

manual testing script #201

Merged
merged 4 commits into from
Nov 7, 2016
Merged

Conversation

nightism
Copy link

@nightism nightism commented Nov 7, 2016

No description provided.

1 | Go to the Command box on the top of the app | | User should be able to type anything here
2 | Write/ Paste the Test Data into the box And press enter| add "testing a program now" p-3 | The added task should be added and highlighted under 'Floating Task' and given a `Priority` of 3.
3 | Repeat step 2 but with a different set of test data | add "this is a deadline" 11/11/2016 11:15pm | the added deadline should be added and highlighted under 'Deadline'
4 | Repeat step 2 one more time but adding a Event this time | add "test cs2103 product" 11/11/2016 4:15pm to 8:20pm | the added event should be added and highlighted under "Event"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add typewriter quotes to the test data

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

? what do you mean...

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nevermind.

Steps no. | Steps | Test Data | ExpectedResult
--- | :---------------- | :---------------- | :----------------
1 | Add a floating task using the test data | add "very flexible" | the task should be added and highlighted under 'Floating Task' given a default priority of 0.
2 | Add a deadline | add cs2103Report 10pm | the dealdine should be added and highlighted under 'Deadline'
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deadline


TestCase ID: TC003 <br>
Title : The Flexibility of adding a task,event ,deadline <br>
Description : Tester should be able to add a task without following a rigid format and natural date language <br>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the "natural date language" part, because our dates are not natural

@nightism nightism added the p.High label Nov 7, 2016
@pyokagan
Copy link

pyokagan commented Nov 7, 2016

@nightism Can add a few more tasks? I think we need 50. Other than that I think we should just merge already.

Title : Searching for task <br>
Description : Tester should be able to search task by their names using keywords. <br>
Format : <br>
`find KEYWORDS [mark/true]` <br>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nightism What is mark?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

1 | create a new empty folder named 'TaskTracker' (or any name you prefer) on any location | |a folder called 'TaskTracker' (or as named) should be created
2 | download the v0.5 jar file and place it inside 'TaskTracker' folder | [Project Releases](https://github.com/CS2103AUG2016-T11-C4/main/releases) |the folder should contain the downloaded jar file
3 | Within the same folder you created, create a new folder called "data" | |A new folder named "data" should be created
4 | Transfer the `SampleData.json` in `ManualTesting` folder and put it in the `data` folder | |The forDemoUse.json file should be inside the `data` folder
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nightism forDemoUse.json?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

3 | Within the same folder you created, create a new folder called "data" | |A new folder named "data" should be created
4 | Transfer the `SampleData.json` in `ManualTesting` folder and put it in the `data` folder | |The forDemoUse.json file should be inside the `data` folder
5 | Rename the `SampleData.json` to `taskbook.json` | |The `SampleData.json` is renamed to `taskbook.json`
6 | open the jar file | |TaskTracker window should appear. config, perferences and log file should be generated in the same folder and some tasks should already be loaded into the system.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have a preferences file.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved


Steps no. | Steps | Test Data | ExpectedResult
--- | :---------------- | :---------------- | :----------------
1 | Default the list to show everything using find command | find type/all | the list should show everything stored in the save data
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nightism find command?????? Should just be list

--- | :---------------- | :---------------- | :----------------
1 | Go to the Command box on the top of the app | | User should be able to type anything here
2 | find task whose name contains `Unicycling` keyword | find 'Unicycling' | TaskTracker will list all tasks whose name contains the keyword
3 | show the command list in command box | TAB | the command list will shown
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the command box empty but selected, press TAB.

A list of commands will pop up.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sloved

1 | Go to the Command box on the top of the app | | User should be able to type anything here
2 | find task whose name contains `Unicycling` keyword | find 'Unicycling' | TaskTracker will list all tasks whose name contains the keyword
3 | show the command list in command box | TAB | the command list will shown
4 | repeat step 2 to select the edit command | TAB | the edit command will be highlighted
Copy link

@pyokagan pyokagan Nov 7, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the list of commands still shown, press TAB to cycle through the items until the edit command.

The edit command will be highlighted.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

2 | find task whose name contains `Unicycling` keyword | find 'Unicycling' | TaskTracker will list all tasks whose name contains the keyword
3 | show the command list in command box | TAB | the command list will shown
4 | repeat step 2 to select the edit command | TAB | the edit command will be highlighted
5 | select the edit command | ENTER | the edit command will be selected and typed into the command box automatically
Copy link

@pyokagan pyokagan Nov 7, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Press ENTER to select the edit command.

the edit command will be selected and typed into the command box automatically

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

4 | repeat step 2 to select the edit command | TAB | the edit command will be highlighted
5 | select the edit command | ENTER | the edit command will be selected and typed into the command box automatically
6 | enter the index number of the target task and then the keyword for task name field | e3 n- |
7 | use auto-complete to load the previous name | TAB | the previous task name will be auto typed in the command box
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Press TAB.

The task name of e3 will be auto typed in the command box.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

--- | :---------------- | :---------------- | :----------------
1 | Add a floating task using the test data | add "very flexible" | the task should be added and highlighted under 'Floating Task' given a default priority of 0.
2 | Add a deadline | add cs2103Report 10pm | the deadline should be added and highlighted under 'Deadline'
3 | Add a event | add "picnic with professor" tdy 11pm to tmr | the event should be added and highlighted under 'Event'.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Event should be added with today 11pm as the start date and tomorrow 23:59 as the end date,

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

--- | :---------------- | :---------------- | :----------------
1 | edit the first floating task and change it name | edit f1 n-clean the window and floor p-4| the edited task should be highlighted reflecting the new changes
2 | edit the first event task | edit e1 st-12am et-11:59pm | the edited task should be highlighted reflecting the new changes
3 | edit the first event task | edit dt-10pm | the edited task should be highlighted reflecting the new changes
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nightism Command seems to be wrong

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably edit d1 dt-10pm

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

Steps no. | Steps | Test Data | ExpectedResult
--- | :---------------- | :---------------- | :----------------
1 | Go to the Command box on the top of the app | | User should be able to type anything here
2 | find task whose name contains `Unicycling` keyword | find 'Unicycling' | TaskTracker will list all tasks whose name contains the keyword
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs to be find "Unicycling" or find Unicycling

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

3 | show the command list in command box | TAB | the command list will shown
4 | repeat step 2 to select the edit command | TAB | the edit command will be highlighted
5 | select the edit command | ENTER | the edit command will be selected and typed into the command box automatically
6 | enter the index number of the target task and then the keyword for task name field | e3 n- |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be precise, maybe say Enter the index number of the target task and then the task name field flag such that the command reads "edit e3 n-"

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

1 | Use the list command to find all unfinished tasks | list unfin | the list should show all unfinished tasks
2 | Mark the task in index d3 as done | fin d3 | the task should be strikethrough and the task is successfully marked as finished
3 | Use the list command to see all finished tasks | list fin | the list should show all finished including the one just marked as finished
4 | Mark the task in index d3 as unfinished | unfin d1 | the strikethrough of that task shoul be disappear and the task is successfully marked as unfinished
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nightism Mark the task in index d3 as unfinished --> unfin d1????

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved, by change d3 to d1

`add FLOATING_TASK_NAME [p-priority]` <br>
`add DEADLINE_NAME MM/DD/YYYY HH:MM[am/pm]` <br>
`add EVENT_NAME MM/DD/YYYY HH:MM[am/pm] to MM/DD/YYYY HH:MM[am/pm]` <br>
Format expanationation: <br>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Format explanation:

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved


Steps no. | Steps | Test Data | ExpectedResult
--- | :---------------- | :---------------- | :----------------
1 | Enter the find by name command | find cs2103 | the list should be updated with all task that contain CS in the name
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The list should be updated with all tasks that contain cs2103 in the name.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved

@pyokagan
Copy link

pyokagan commented Nov 7, 2016

@nightism Okay let's finish this

@pyokagan pyokagan merged commit 2d8ab43 into CS2103AUG2016-T11-C4:master Nov 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants