aizatazhar / pe Goto Github PK

Description

• When having multiple tags in a contact, the tags some times don't follow alphabetical order

Steps to reproduce

1. enter addcontact n/Amanda Jo p/81234567 e/[email protected] a/PGP House c/Facebook t/Friend t/Abc t/abc

Expected outcome

• Tags arranged alphabetically

Actual outcome

• Tags not arranged alphabetically

On page 17,

Return arrows should be dashed

Description

• UG does not specify what counts as a duplicate person in the contacts, so it is reasonable to think that we can add 2 people who may have the same name but different phone number/address.

Steps to reproduce

1. Enter addcontact n/Amanda Jo p/81234565 e/[email protected] a/PGPP House c/Facebook t/friend
2. Enter addcontact n/Amanda Jo p/99999999 e/[email protected] a/PGPP House c/Facebook t/friend

Expected outcome

• Both are able to be added

Actual outcome

• This person already exists in the address book

Description

• The command given in section 3.1. step 5 bullet point 2 is invalid

Steps to reproduce

1. Enter add_contact n/John Doe p/98765432 e/[email protected] a/John street,block 123, #01-01 c/ABC Holdings Pte. Ltd

Expected outcome

• Adds a contact named John Doe to the AddressBook

Actual outcome

• Unknown command

In section 4.2.10

should be effective instead of effectively

It mentions "...where the user issues the command deletemeeting 1" but the sequence diagram shows the command delete 1 being executed by the user instead

Description

• deletemeeting accepts invalid dates such as 30/02/20, 31/02/20, 31/11/2020 etc.

Steps to reproduce

1. Enter addmeeting title/roundtable discussion d/30/02/20 1200 dur/00 30 l/NUS SoC

Expected outcome

• Error message saying the date does not exist

Actual outcome

• Meeting is created

UG uses numbering e.g. 5.0, 5.1 while DG uses bullet points

On page 23, the following class diagram is provided where Command is shown as a concrete class

however, on page 7 it is mentioned that Command is abstract

Description

• The error message given says the date format should be d/m/yy whuch contradicts the example given since the example has format dd/m/yy.
  

Steps to reproduce

1. enter editmeeting 2 d/12/12/20 1200

Additionally, the following command is valid: editmeeting 2 d/12/0000012/20 1200

As shown at the green arrow, the sequence diagram says deletemeting instead of deletemeeting

Have a meeting scheduled within the next 30 mins (round table discussion at 5.30pm), restarted the app and waited more than 1 minute but no popup was shown as stated in the UG

5:13pm

5:14pm

5:15pm

Description

• When using deletemeeting 0123456789, we get correct error message of The meeting index provided is invalid but when doing deletemeeting 012345678901 we get the generic invalid deletemeeting command format

Steps to reproduce

1. enter deletemeeting 0123456789
2. enter deletemeeting 012345678901

Expected outcome

• Both should have the same error message of the meeting index provided being invalid

Actual outcome

• Different error messages

Description

• Depending on the index provided, the error message differs

Steps to reproduce

1. deletepart ci/3933333333 mi/1
2. deletepart ci/400 mi/1

Expected outcome

• Same error message that there is no such participant in the meeting

Actual outcome

• Different error messages

Description

• When restarting the app, the order of the contacts changes

Steps to reproduce

1. Enter addcontact n/Amanda Joo p/81234567 e/[email protected] a/PGP House c/Facebook t/friend r/help. In this case Amanda Joo is added as 12th person in the addressbook
   
2. exit
3. Restart the application
4. Amanda Joo is now 6th in the addressbook

Expected outcome

• Ordering is preserved

Actual outcome

• Ordering is not preserved

Description

• UG states that the duration must be in the format H mm
  

but example some commands gave HH mm format and additional leading zeroes are also allowed

Steps to reproduce

1. addmeeting title/TEST d/29/02/20 0000 dur/0009 00011 l/NUS SoC

Expected outcome

• Error message since duration is not in specified format

Actual outcome

• Command is accepted