duckwillow / pe Goto Github PK

At beginning, I found this when key in weekdays.

Only 'Friday' or 'friday' should be allowed in the schedule. Keep the format the same!

The same problem happens in the timetable function.

Then I realize all uppercase and lowercase is mixed up together.

After CS2113T is added, command for module is shown not found.

'module' should not be a non-valid command. It should be a global command because that's the program's key feature.

The accepted input for the argument includes “Monday”, “Tuesday”, “Wednesday”, “Thursday”, “Friday”, “Saturday”, and “Sunday”.

However, during testing, "monday" is also accepted.

Time 24:00 should be rejected.

Set time should regard 24 hours as invalid time.

Should tell the user not to type in those characters that can't be displayed.

Nice try to detect 'The <zoom_link> must begin with a “http://” or “https://” in order for the link to be valid.'
But more effort should be put in to detect valid website.

The file name with a special character not being reloaded in the note.

Module and Note function share the same command, it sometimes confuse user. Try different command such as 'view module' and 'view note'.

In the design, a note must contain a name and content.

But using reload function will allow user to create a empty note with name but no content.

There should be at least some restriction for the module input. A single char 'C' or ',' can never be a real module code. Don't code as if it's just a project, code as if it's your company product and you will serve the real people.

Uppercase is for Class.

No details provided by bug reporter.

Conflict schedule should not be added.

I only have 1 question on the list, but I want to test 233 questions. Should throw outofrange exception.

hint format: add "<module_code>"
User will think use add ""
but the real format is add "CS2113T"