Refactoring code in src/middleware/render.js to Reduce Cognitive Complexity from 16 to 15

[vickyc2266]

Reduced cognitive complexity of the renderMethod which is within the processRender function of the render.js file by taking away a conditional that appears in the code more than once and putting it into a helper function with an intuitive title called checkHeadersSent(res). The function here is supposed to provide the same exact logic as the original code but just putting it in into a function and calling that function where it is needed.
resolves #340

UI Test

1. Login Successfully as admin
2. Able to Run Server Successfully
3. Able to access different and render different UI pages

[coveralls]

Pull Request Test Coverage Report for Build 10722278560

Details

• 6 of 7 (85.71%) changed or added relevant lines in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.003%) to 82.674%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/middleware/render.js	6	7	85.71%

Files with Coverage Reduction	New Missed Lines	%
src/meta/errors.js	1	76.74%

Totals
Change from base Build 10607818019:	0.003%
Covered Lines:	22327
Relevant Lines:	25585

---

💛 - Coveralls

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[vickyc2266]

I'm not sure why I'm missing a line of code coverage (from the pull request details above) from the code I've added to the file because this issue I've chosen is extremely difficult to test since it has to do with the rendering of the UI users sees and validates whether a response header has been sent. In the test > middleware.js file where I believe locates all the test cases for code that's in the middleware folder of src, I tried to add test cases that tests the code I've added (regarding the conditions of the resHeader) by making mock data and mock headers. Although I've set these headers to true and asserted the outcome to be true, the coverage file for some reason is still warning me that I haven't tested when the case is true.

From the screenshot provided above, the only line of code that's written by me and highlighted red would be "return true" statement which I do test in the test case example provided in the screenshot below: