Reference no: EM133655852

Software Design & Development

Assessment item: Software design implementation

Brief
This form is designed to capture individual contributions towards the assignment. Your assignment will receive an overall score, which will be adjusted based on peer assessment to give you a final score. This final score will be part of your overall grade.

Instructions
- Fill in the required identification fields.
- Write a brief description of your contributions to the assignment.
- Show this summary to your teammates, and read theirs' at the same time. Each team member must sign to acknowledge he or she has read it.
- Without showing your teammates, fill in the allocation table at the bottom. Distribute the 100 points across all team members including yourself - put yourself first on the list - in proportion to the contribution you believe they (and you) have made.

Software Testing Report:

Description Upon application start up, the user shall be presented with an interactive list of researchers (consisting of both staff and research students), known hereafter as the Researcher List view

Criteria - When starting the application, the user will be presented with an interactive list of researchers (including staff and researchers Students), hereinafter referred to as the List of Researchers views. This list will display names in "Last name, first name (Title)" format, as in "Einstein, Albert (Dr)". The job ranks correspond to the following job titles: (A, research associate), (B, lecturer), (C, associate professor), (D, associate professor), and (E, teacher). The user will be able to filter the researcher list view based on the researcher's employment level or student status. Users can list all researchers, students only, A grade, B grade, C grade, D grade, and E grade. The usefulness of the system would be improved if the user could filter the list by entering part of the researcher's name. The contents of the list will be restricted to only showing employees whose first or last name contains the text entered by the user. There is no need to support partial matches
consisting of first and last name combinations.

Method - Black-Box Test:
Open the RAP System
Verify that the Researcher List view is visible and properly cleared on the screen.
Check if the researcher entries are displayed in a visually organized manner, such as in a table, list, or grid format.
Verify that each researcher's entry includes their name, and employment level.
Verify that the displayed information for each researcher is accurate and matches the corresponding details from the researcher list.
Check for any formatting or display issues, such as short forms of text or overlapping elements.
Repeat the above steps for different screen resolutions to ensure the Researcher List view remains properly displayed.

Method - Black-Box Test:
Start the application.
Navigate to the Researcher List view.
Verify that the Researcher List view is visible.
Check if the researcher entries are displayed in a visually organized manner, including name, and employment level.
Apply a filter for the employment level by selecting level "C" from the options.
Verify that the Researcher List view updates and displays only the researchers whose employment level matches the selected filter ("C").
Compare the displayed researchers with the expected list of researchers with employment level "C" and ensure they match.

Outcome - Upon comparison, it is found that some researchers with employment level "C" are missing from the displayed list. The filter does not accurately filter the researchers based on the employment level "C". And an issue with the implementation of the employment level filter
functionality.
White Box Test:
Open the RAP system and access the source code.
Review the code responsible for student-only filtering
the Validate that the sorting logic in the code is correctly implemented, considering all possible edge cases and scenarios.
Apply the filter for students only and ensure that the researcher list is updated to show only research students.
Verify that the displayed researchers have the "student" status and adhere to the name formatting.
Run the white box test cases and observe the behavior of the system, comparing it with the expected outcomes based on the code analysis.
Document any discrepancies or bugs found during the white box testing process.
Repeat the steps above if necessary, making any required modifications to the code or test cases until the desired level of
quality is achieved.