Test cases 8 to 20 to create an Announcement in a web app, android app and google app: Processes against Announcement with type Lost: Create an Announcement (Found Case)

Create an Announcement (Found Case) :

Test Case-8:

While creating an announcement user adds a question. User asks When have lost your pse? In this question there is a spelling mistake in PURSE. User wants to correct it.

Expected result:

User click on the place where he wants to make a change. System should let the user fix this spelling mistake at a single focus.

Actual result:

User clicks on the place and just tries to enter U then tries to enter R but actually our system changes the focus at the end of the line and for completing a spelling again and again user have to makes his/her focus at that place. This is wrong.

Status: Fail

Test Case-9:

User has created an announcement. Now user comes in his/her activities tab there he/she select his/her announcement and gives his/her comments against that announcement.

Expected result:

System should accept the comments and should update the announcement’s comments in comment tab portion.

Actual result:

System accepts the comments but does not update the comment count in the comment tab until unless user does not change the whole screen and comes back to the activities tab and selects the comment.

Status: Fail

 

Test Case-10:

User has created an announcement by providing its description and in activities tab there finds a tab named Details. User clicks on that button to view details of that announcement.

Expected result:

While user clicks on the Details tab then description or characteristics of the announcement entered by the announcement creator should appear to the user.

Actual result:

There is no description or there are no characteristics appear in that portion.

Status: Fail

Test Case-11:

User creates an announcement for a found product and after creating it, user edits it by going in his/her activities and update it with or without making changes in it. Test data is as followed.

  • Name/Title: Ladies purse
  • Location: Islamabad
  • Images: 7 different images attached.
  • Description/Characteristics: This is a lady purse, black in color.

There added 5 different length questions as followed added here

  • When have you lost your purse?
  • What things were in the purse?
  • Exactly describe the condition of the purse and exactly tell the location of the purse where you had lost it.
  • There are some tags on the purse. Please tell at least two correct tags
  • There is an identity card in it. Please tell me the correct CCV number.

Expected result:

Application should accept the update process with a success message.

Actual result:

Application does not show the expected behavior and crashes out.

Status: Fail

Note: Crashing of application is probably due to uploading more images.

 

Test Case-12:

User has created an announcement for a found product and enters more than one question in it. Now user goes in activity tab and edits that announcement. There one by one user removes all questions entered by the user.

Expected result:

For all questions in edit mode there should be a CROSS SIGN appear to remove them easily.

Actual result:

At early end when last question remains there then there is no Cross sign appears to remove that question and user has to remove that manually.

Status: Fail

 

Test Case-13:

User uploads more than one images. Suppose user adds 15 images against an announcement. Now user deletes an image placed on the index number 7.

Expected result:

System should let the user to delete that pic placed on the index number 7 and should not change the user’s focus from index number 6 image or 5 image so that a user would not have to come again at the same index number by swapping the images.

Actual result:

After deleting a  an image placed on the index number 7 system brings the user at the end of the images upload and user has to come back at the old place to view its left place of images. This irritates a lot to the user. User’s focus should not change.

Status: Fail

Test Case-14:

User created an announcement and now after sometime or due to some reason user closed that announcement. Now user comes again and tries to edit everything related to that announcement.

Expected result:

System should let the user to edit anything related to the announcement because now there our system does not allow us to change the status of that announcement, which means that now user can do nothing with that closed announcement.

Actual result:

System allows a user to edit that announcement which has closed. This should not happen.

Status: Fail

Test Case-15:

User created an announcement for a lost product or a thing. User makes it status Closed, Hand Over or Delivered.

Expected result:

Now system should not allow the user to edit this announcement.

Actual result:

System allows to edit the announcement.

Status: Fail

 

Test Case-16:

User created an announcement for a lost product or a thing. User makes it status Closed, Hand Over or Delivered.

Expected result-1:

Now system should not allow the user to edit this announcement.

Actual result-1:

System allows to edit the announcement.

Status: Fail

Expected result-2:

When user delivers the product to the concern person then there should be no option there and after mark Deliver announcement should be a history and always treated as closed automatically.

Actual resut-2:

System allows to deliver again after once a user has delivered the product.

Status: Fail

 

Test Case-17:

In our PK BAZAAR there exist different categories and their subcategories as well.

Expected result:

Categories and their subcategories headings should be singular not plural accordingly.

Actual result:

Categories are not singular. They are plural.

Status: Fail

Test Case-18:

In our Crowd against a category named People, if a person goes to create an announcement for a Lost Case or for a Found Case. Then there are four sub-categories there named Man, Woman, Boy and Girl. User goes with category named Man and see a filing form. Then user creates another announcement against other sub-categories.

Expected result:

Against all categories there should be a consistency in fields appearing against category Man and others.

Actual result:

There is no consistency of fields under all sub-categories of main category named People.

Status: Fail

 

Test Case-19:

User creates an announcement for category Incident. User tries to upload images.

Expected result:

Images should be uploaded.

Actual result:

Images do not upload.

Status: Fail

 

Test Case-20:

User creates an announcement for category Incident. User tries to update announcement.

Expected result:

Announcement should be updated.

Actual result:

Announcement does not update.

Status: Fail

Add a Comment

Your email address will not be published. Required fields are marked *