Manual Testing: Console testing on google chrome (User Story 2)

[lhitmi]

During this sprint, we encountered challenges that led us to scrap the initial database concept. Instead, we adapted the code to handle data directly through the controller on the page. However, we still faced issues, which prompted us to conduct manual API testing to ensure everything was working.

In Google Chrome, using the Console tab, we executed the following command to check the GET API's response:
fetch('http://localhost:4568/api/admin/get-bug-log')
.then(res => res.json())
.then(console.log)

This command allowed us to observe how the GET API behaved. We received a response containing relevant information such as the uid, username, and login status, confirming that the data was being received. The results are shown in the screenshot below:

We also verified this through the Network tab when submitting the form with the data we entered, as shown in the following screenshot:

The GET request function can be further verified by the following screenshot showing that data is being fetched upon submission:

You can clearly see in the console that the submitted data was fetched.

We can also see it when running a command on the console as shown by this screenshot

this is the error we are receiving that is blocking the post

Contributors to this pull request:

• Aisha Al Attiyah
• Ahmad Al Obaidan
• Latifa Al Hitmi

This pull request resolves issue #40

[coveralls]

Pull Request Test Coverage Report for Build 11420912120

Details

• 8 of 22 (36.36%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.03%) to 82.652%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/controllers/admin/dashboard.js	6	20	30.0%

Totals
Change from base Build 11057241668:	-0.03%
Covered Lines:	22361
Relevant Lines:	25636

---

💛 - Coveralls

[akobaidan]

the code looks good so far.