nus-cs2103-AY2223S2 / pe-dev-response

1 stars 0 forks source link

Schedule command ignores the simple tasks #4247

Open nus-pe-bot opened 1 year ago

nus-pe-bot commented 1 year ago

schedule command ignores the simple tasks which never diplays the simple tasks to be competed.


[original: nus-cs2103-AY2223S2/pe-interim#3998] [original labels: severity.Medium type.FeatureFlaw]

Huggenguggen commented 1 year ago

Team's Response

Hello, we are unable to replicate the issue you mentioned about schedule not allocating SimpleTasks because you have not given any information about what you did, or what commands you entered for the said issue to occur.

We included some sample for testing in our developer guide, appendix: instructions for manual testing. Perhaps you could have used that as a starting point to test the schedule feature in the PE to verify its behavior. As a tester/user, there are several other ways you could have checked if SimpleTasks were actually being allocated. Some examples include: 1) Checking the planner.json file within the data folder to see if SimpleTasks are stored in the storage of a generated schedule. 2) Use the schedule command to check through 30 days of generated plans, to see if a SimpleTask was left out of the allocation.

Another simple way to check if SimpleTasks are indeed allocated using the schedule command, is to enter 'schedule D/{current date} E/10' on starting the application. You will be able to see tasks allocated to the schedule for the current date.

Again, as (1) you did not include any information about the steps to reproduce the claimed behavior that 'schedule command ignores the simple tasks', (2) our team specifically mentioned ways in which testing can be done in our developer guide to test the behavior of schedule and it directly contradicts your claims, (3) there are multiple other ways for testers to test this feature (as explained above), we are rejecting this bug report as we have proven the correct behavior (schedule considers simpletasks) multiple times and are unable to reproduce this issue with the information/steps you provided.

Duplicate status (if any):

--