Closed ElecTwix closed 1 year ago
Hi @ElecTwix I went through your changes and I wanted to suggest some changes.
1) I feel 50 is a small number to test concurrency with and would suggest you increase the number of coroutines? To ensure high levels of concurrency. 100 seems like a good number. 2) Is it possible to change the 3 tests into a single test based on different scenarios? 3) The scenario is loop 1..100 select => no row error create select => validate 4)There is a single wait group that is shared between 3 tests, this can introduce race conditions.
@timpratim Thanks for your review, I think we should review this in #69, this PR just GoReport.
- I feel 50 is a small number to test concurrency with and would suggest you increase the number of coroutines. To ensure high levels of concurrency. 100 seems like a good number.
That suits me.
- Is it possible to change the 3 tests into a single test based on different scenarios?
Far as I remember we were doing unit testing, not a stress test if that's the case I can move some tests to another file.
- There is a single wait group that is shared between 3 tests, this can introduce race conditions.
Unfortunately, we are using testify's test suite and we cannot run all tests like race conditions in the unit test it needs to be cleaned up after every unit test.
Hi, @ElecTwix , thank you for your contribution to this PR. Could you please consider removing the websocket test from this particular PR? It would be beneficial to keep this PR focused on Goreport for better clarity in tracking changes.
Since the review comments have already been addressed in #69, it would be great if we could track the websocket test there instead. This will help reduce redundancy.
Hi, @ElecTwix , thank you for your contribution to this PR. Could you please consider removing the websocket test from this particular PR? It would be beneficial to keep this PR focused on Goreport for better clarity in tracking changes.
Since the review comments have already been addressed in #69, it would be great if we could track the websocket test there instead. This will help reduce redundancy.
converted to draft PR when other PR has been merged then I can rebase and open the PR.
@timpratim this PR ready for review.
Goreport added for code quality display