Closed JayNakrani closed 10 years ago
Maybe it would be good idea to enable travis on your repository as well to get the test results during development. Just go to travis-ci.org, register there and enable testing for your repository.
Also please try to not make our code worse, looking at the Coveralls and Scrutinizer inspection, you've lowered test coverage by 9% and introduced some code issues (code duplication and introduced unused variable).
I've enabled travis-ci on my repository. I did't mean to make the code worse. I thought I'd fix all the failing tests this week and write the new test cases next week. Anyway, by the end of the next week probably those issues won't be there.
@nijel : In testCreateIncidentFromBugReport()
, I could not find a solution to do initialization in Mock objects. So, I've changed the test to use actual objects. The tasks in TODO will be pushed shortly.
Right now I'm having problem in saving the closest report before case-2. See this build log for more details.
The inspection completed: 2 new issues, 1 updated code elements
Looks good, I've merged it and deployed on reports.phpmyadmin.net.
Please implement the missing tests, so that we get all these cases covered.
BTW: I've found another issue to fix in the code: https://github.com/phpmyadmin/error-reporting-server/issues/50
Commits for review only. Would correct coding standard issues first.