Automated testing for bug log page (User Story 2)

[lhitmi]

I have created automated tests that cover all the functionalities of the public/admin/dashboard/bug-logs.js page, including data storage. The tests are located in test/bug-logs.js.

These tests use a mock document object to simulate a browser environment. A custom querySelectorAll method is defined to return mock elements for specific selectors, such as #bug-logs-container and #bug-report-description. These mock elements replicate basic properties and methods of real DOM elements, ensuring realistic simulation for testing purposes.

This completes issue #39

[coveralls]

Pull Request Test Coverage Report for Build 11496174786

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 17 of 36 (47.22%) changed or added relevant lines in 4 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.04%) to 82.643%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/topics/create.js	6	9	66.67%
src/controllers/admin/dashboard.js	6	22	27.27%

Files with Coverage Reduction	New Missed Lines	%
src/socket.io/topics.js	1	89.92%

Totals
Change from base Build 11057241668:	-0.04%
Covered Lines:	22370
Relevant Lines:	25650

---

💛 - Coveralls

[aattiyah]

Looks good to me

[akobaidan]

The tests cover all key functionalities of the bug-log feature and behavior, specifically addressing data storage.

The use of querySelectorAll to mock and return elements, such as #bug-logs-container and #bug-report-description effectively simulates the environment to validate functionality. Moreover, realistic simulation of DOM interactions with mock elements guarantees that the page behaves correctly with regards to data handling.

This approach keeps the tests thorough and isolated from external dependencies. Thus, the code is ready for merging.