|
|
If you develop new features in Alya, you should regularly add new tests to the testsuite to validate that such a feature works as expected, but also that nobody breaks this feature when contributing to Alya. We won't accept complaints from someone whose Alya features are not evaluated by the testsuite, because it is not reasonably possible to determine all the interweaving between Alya components and the impact of a modification on the whole code behavior without automatic testing. Nevertheless, regarding the developer, we don't validate either the following assertion: _because Alya passes the testsuite, my contribution is of good quality_. Any contribution should be thought, designed carefully without interfering with the normal behavior of Alya, and if possible mentioned to the design team through the issues.
|
|
If you develop new features in Alya, you should regularly add new tests to the testsuite to validate that such a feature works as expected, but also that nobody breaks this feature when contributing to Alya. We won't accept complaints from someone whose Alya features are not evaluated by the testsuite, because it is not reasonably possible to determine all the interweaving between Alya components and the impact of a modification on the whole code behavior without automatic testing. Nevertheless, regarding the developer, we don't validate either the following assertion: _because Alya passes the testsuite, my contribution is of good quality_. Any contribution should be thought, designed carefully without interfering with the normal behavior of Alya, and if possible mentioned to the design team through the issues.
|
|
|
|
|
|
|
|
# Add a new test
|
|
# Add a new test or modify an existing one
|
|
|
|
|
|
|
|
Tests are located to the following path:
|
|
Tests are located to the following path:
|
|
|
```
|
|
```
|
|
|
svn co svn+ssh://bsc21***@mn3.bsc.es/gpfs/projects/bsc21/svnroot/AlyaTS/Trunk
|
|
svn co svn+ssh://bsc21***@mn3.bsc.es/gpfs/projects/bsc21/svnroot/AlyaTS/tests
|
|
|
```
|
|
```
|
|
|
```
|
|
```
|
|
|
svn co file:///gpfs/projects/bsc21/svnroot/AlyaTS/Trunk
|
|
svn co file:///gpfs/projects/bsc21/svnroot/AlyaTS/tests
|
|
|
```
|
|
```
|
|
|
|
|
|
|
|
However, you cannot contribute to this repository. So you will have to create a new branch as it follows:
|
|
|
|
|
|
|
|
```
|
|
|
|
svn copy svn+ssh://bsc21***@mn3.bsc.es/gpfs/projects/bsc21/svnroot/AlyaTS/tests svn+ssh://bsc21***@mn3.bsc.es/gpfs/projects/bsc21/svnroot/AlyaTS/branches/[mytests]
|
|
|
|
```
|
|
|
|
|
|
|
|
replacing `mytests` by the name you want.
|
|
|
|
|
|
|
|
If you already have your own tests branch, update it using the merge command:
|
|
|
|
|
|
|
|
```
|
|
|
|
svn update
|
|
|
|
svn merge svn+ssh://bsc21***@mn3.bsc.es/gpfs/projects/bsc21/svnroot/AlyaTS/tests
|
|
|
|
svn commit
|
|
|
|
```
|
|
|
|
|
|
|
|
## Modify an existing test
|
|
|
|
|
|
|
|
Go to the test directory, and modify the test files and the test .json consequently.
|
|
|
|
Then, commit, and run a testsuite on your test branch to validate your changes. Once it's done, ask the admin to reintegrate your changes. The admin automatically receive the testsuite emails (if you run it on your machine) so you won't have to justify that it ran with success. |
|
|
|
\ No newline at end of file |
