Important links:

JIRA: https://opendce.atlassian.net/projects/QS

Source Code: https://bitbucket.org/opendce/qualityspy

Static Code Analysis: http://snow.iiar.pwr.wroc.pl:8081

Old project page: https://java.net/projects/qualityspy

Tests implementation

Unit tests

JUnit tests are the simple and fast tests that use mocks to check simple, single functionality. You should write JUnit to check every function that you use in your code. JUnit must be fast, it should be matters of seconds to run that test. Naming param is *className*Test.java

Integration tests

Integration tests are here to check whenever the functions that you use in code work well together. Those tests may take longer to run. In maven they are run in integration-test phase. Naming param is *className*IT.java, or you can use IntegrationTest instead IT, if you would like.

Acceptance tests

You write acceptance tests to check if your code fulfill, the requirements of project. Naming param is *className*Acceptancetest.java, we run these tests in integration-test phase.

Database

Simple configuration of the database can be found here.

Configuration Parameter

Configuration Parameter - Step by step

There is a simple instruction how to add new configuration parameter.

First of all You have to open project, next go to quality-spy-common - its GUI module.

Next click: Source Packages and choose Propertis.java

Here You have screen how to add test parameter to project, its very simple:

Function getaddTestHomeKey return string, this string will be show in program.

OK, if You done this, go to next step.

You have to add Key() function:

TODO: getaddTestSeparator should be remove.

Please open ConfigJPanel.java file and type code similar to this. By this function You add row to Your table.

Well done, if You do not mistake it should be look like this:

TODO: There are component dedicated interfaces with subsets of parameters that should be updated.