Damith C. Rajapakse
Damith C. Rajapakse
Currently, we ask students to add a test script and a test data file near the final submission. We can integrate it to the dev guide (e.g. as an appendix),...
The example code we give for component enhancements don't have tests. We should mention that in the dev guide and ask the reader to implement tests as well. Alternatively, we...
Current: >For Import Layout: The order is import static all other imports, import java.*, import javax.*, import org.*, import com.*, import all other imports. Add a between each import Suggested...
As auto-publishing of docs is triggered by new commits to the master branch, docs of a fresh fork will not be published until there is a new commit. Is there...
see https://github.com/nus-cs2103-AY1718S1/forum/issues/61 In dev guide we can either give instructions to avoid this problem or how to troubleshoot and rectify.
If the user resizes the App, the new size is retained the next time the App is run. This behavior is not tested in our system tests and therefore can...
Currently we are using codacy. Explore using sonarcube instead.
Create one PR for each Test class. * PR name can be `Add unit tests for {ClassName} class` e.g `Add unit tests for Foo class` * Omit the `Fixes #....`...
Suggestion: Add some logging statements lower that INFO level, to illustrate the use of various logging levels.
Problem: We had to drop Coveralls support when we moved from Travis to GitHub Actions. Suggestion: We can add some kind of coverage reporting to CI.