1.

Test Case 1: File name does not exceed 50 characters and file size does not exceed 20
MB, file format is CSV.
o Input:
 File Name: "example_file.csv"
 File Size: 10 MB
 File Format: CSV
o Expected Output:
 Prompt message: "Upload the file to storage"
 Success message: File uploaded successfully.
2. Test Case 2: File name exceeds 50 characters and file size does not exceed 20 MB, file
format is CSV.
o Input:
 File Name:
"this_is_a_very_long_file_name_that_exceeds_the_maximum_allowed_c
haracters.csv"
 File Size: 10 MB
 File Format: CSV
o Expected Output:
 Error message: "File name should not exceed 50 characters."
3. Test Case 3: File name does not exceed 50 characters and file size exceeds 20 MB, file
format is CSV.
o Input:
 File Name: "example_file.csv"
 File Size: 25 MB
 File Format: CSV
o Expected Output:
 Error message: "File size should not exceed 20 MB."
4. Test Case 4: File name does not exceed 50 characters and file size does not exceed 20
MB, file format is JSON.
o Input:
 File Name: "example_file.json"
 File Size: 10 MB
 File Format: JSON
o Expected Output:
 Prompt message: "Upload the file to storage"
 Success message: File uploaded successfully.
5. Test Case 5: File name does not exceed 50 characters and file size does not exceed 20
MB, file format is not CSV or JSON.
o Input:
 File Name: "example_file.txt"
 File Size: 10 MB
 File Format: TXT
o Expected Output:
 Error message: "File format should be CSV or JSON."
 6. Test Case 6: File name exceeds 50 characters and file size exceeds 20 MB, file format is
not CSV or JSON.
o Input:
 File Name:
"this_is_a_very_long_file_name_that_exceeds_the_maximum_allowed_c
haracters.txt"
 File Size: 25 MB
 File Format: TXT
o Expected Output:
 Error message: "File name should not exceed 50 characters."

Note: For each test case, you can modify the input parameters based on the specific requirements
of your system and add additional test cases if needed.

Certainly! Here's a test case table that covers different paths based on the given scenario:

Test Case File Name File Size File Format Expected Output
Prompt message: "Upload the file to
1 "example_file.csv" 10 MB CSV
storage"
Success message: File uploaded successfully
Error
message:
"File
10 name
"this_is_a_very_long_file_name_that_exceeds_the_maximum_allowed CS
2 M should
_characters.csv" V
B not
exceed 50
character
s"
3 "example_file.csv" 25 MB CSV Error message: "File size should not exceed 20 MB"
4 "example_file.json" 10 MB JSON Prompt message: "Upload the file to storage"
Success message: File uploaded successfully
Error
message:
"File
10
TX format
5 "example_file.txt" M
T should
B
be CSV
or
JSON"
6 "this_is_a_very_long_file_name_that_exceeds_the_maximum_allowed_ch 25 TX Error
aracters.txt" M T message:
B "File
 Error
message:
"File
10
TX format
5 "example_file.txt" M
T should
B
be CSV
or
JSON"
name
should
not
exceed 50
character
s"

Note: This table covers the test cases mentioned earlier. You can add more test cases if needed or
modify the input parameters to match the requirements of your system.

A customer support agent has just reported that a customer was unable to see the contacts that he
has added in the platform when it was submitted via the Contact form. The customer claims that
the form was submitted successfully but the Contact was not present on the platform. Based on
the given reported issue and the application flow, list down te steps and approach you will take to
identify the root cause of this issue. Assuming that you were able to replicate the issue and have
identified the root cause of the issue is due to the queue failing, provide a sample bug report that
you will raise in Jira.

To identify the root cause of the issue where the contacts are not appearing on the platform after
submitting the Contact form, you can follow these steps:

1. Replicate the issue:

o Submit the Contact form using the same steps as the customer reported.
o Verify that the Contact is not displayed on the platform after successful
submission.
2. Analyze the reported issue:
o Review the customer's claim that the form was submitted successfully but the
Contact was not present.
o Gather any additional information provided by the customer or the customer
support agent regarding the issue.
3. Review the application flow:
o Understand the end-to-end flow of the Contact form submission process.
o Identify the components and systems involved in processing and displaying the
submitted Contacts.
o Identify any potential points of failure or dependencies.
4. Conduct a root cause analysis:
o Identify possible areas where the issue could have originated, such as database
operations, backend processing, or frontend rendering.
o Inspect server logs, error logs, and any relevant logging mechanisms to identify
any error messages or exceptions related to the Contact submission process.
o Debug the application code to trace the flow and identify any anomalies or errors
that may be causing the issue.
o Perform any necessary tests or checks to validate the data flow and ensure data
integrity.
5. Verify the root cause:
o Once you have identified the root cause, perform further tests to validate your
findings.
o Ensure that the issue is consistently reproducible with the identified root cause.

Sample Bug Report in Jira:

Title: Contacts not appearing on platform after successful submission

Description: Steps to Reproduce:

1. Go to the Contact page on the platform.

2. Fill out the Contact form with valid information.
3. Click on the Submit button.
4. Verify that the success message is displayed.
5. Check the platform to see if the submitted Contact is displayed.
Expected Result:

 The Contact should be displayed on the platform after successful submission.

Actual Result:

 The Contact is not displayed on the platform, even though the form submission is
reported as successful.

Root Cause Analysis:

 After investigating the issue, it was identified that the queue responsible for processing
and displaying the submitted Contacts is failing.

Impact:

 Customers are unable to see their submitted Contacts, leading to potential loss of
important information and customer dissatisfaction.

Attachments:

 Server logs showing errors related to the queue failure.

Severity/Priority:

 Based on the impact and urgency, I recommend setting the severity to High and priority
to Urgent.

Next Steps:

 Investigate and fix the queue failure issue to ensure that submitted Contacts are processed
and displayed correctly on the platform.
 Perform thorough testing to validate the fix and ensure data integrity.
 Communicate the status and progress of the investigation and resolution to stakeholders.

https://www.propertyguru.com.my/property-listing/hentian-kajang-for-rent-by-melissa-yong-33566055