Execute-the-Testsuite.md

@@ -61,9 +61,17 @@ or
 ./configure --all
 ```
 
-Also, if your configuration file is obsolete, you will be asked to run the `./configure --all` again when you launch the testsuite.
+Running 
 
-Here are the different values you will be asked to provide when configuring the testsuite. Note that typing enter without any will use the default option, when it is possible.
+```sh
+./configure --ALL
+```
+
+will give you access to more configuration options.
+
+If your configuration file is obsolete, you will be asked to run the `./configure --all` again when you launch the testsuite.
+
+Here are the different values you will be asked to provide when configuring the testsuite. Note that typing enter without any will use the default option, when it is possible. The option in _italic_ are only proposed when running `./configure --ALL`
 
 #### Marenostrum user
 
@@ -73,12 +81,12 @@ Something like `bscxxxxx`. No default.
 
 Your bsc email. No default.
 
-#### Tests git repository url (ssh)
+#### _Tests git repository url (ssh)_
 
 This is the url of the git repository that contains the tests to run. The default url is [git@gitlab-internal.bsc.es:alya/alya-tests.git] but you can define another repository if it follows the testsuite format.
 This url is used for ssh connections only. See the next section for html connections.
 
-#### Tests git repository url (https)
+#### _Tests git repository url (https)_
 
 Alternate git repository with https. Will be used if the ssh is not possible. The default url is [https://gitlab.bsc.es/alya/alya-tests.git].
 
@@ -86,22 +94,15 @@ Alternate git repository with https. Will be used if the ssh is not possible. Th
 
 The user to connect to the git repository through the html connection.
 
-#### Tests git repository branch
+#### _Tests git repository branch_
 
 If you added or modified tests in a branch of the tests git repository you have defined in the previous section, you can specify the name of this branch. Note that running the testsuite on a custom branch or repository will not count as validation before a merge request.
 
-#### Job queue
-
-This option determines the job queue used to run the testsuite jobs on marenostrum.
-
-*  `debug`: the jobs have more priority but only one can run at the same time. Useful when the marenostrum queue is overloaded or if you run only one or a few subsets of tests.
-*  `bsc_case`: the jobs have less priority but several jobs can run simultaneously. Recommended when the marenostrum queue is not saturated. This is the default option.
-
 #### Alya branch
 
 Type the branch name of Alya you want to test. Don't write the full path, just the name of the branch (for instance, type pre-Trunk for the branch `file:///gpfs/projects/bsc21/svnroot/Alya/branches/pre-Trunk`). `Trunk` by default.
 
-#### MN login
+#### _MN login_
 
 Type one the marenostrum login node among:
 
@@ -111,7 +112,7 @@ Type one the marenostrum login node among:
 
 If you press enter without typing anything, the default value `mn2.bsc.es` will be automatically selected.
 
-#### P9 login
+#### _P9 login_
 
 Same as for marenostrum, but this one for the p9 cluster. Chose between:
 
@@ -121,6 +122,13 @@ Same as for marenostrum, but this one for the p9 cluster. Chose between:
 the default value being `p9login2.bsc.es`.
 Note that you don't have access to p9 by default. We recommend asking for access to the support since it is crucial that Alya compiles and runs well on this architecture.
 
+#### _Job queue_
+
+This option determines the job queue used to run the testsuite jobs on marenostrum.
+
+*  `debug`: the jobs have more priority but only one can run at the same time. Useful when the marenostrum queue is overloaded or if you run only one or a few subsets of tests.
+*  `bsc_case`: the jobs have less priority but several jobs can run simultaneously. Recommended when the marenostrum queue is not saturated. This is the default option.
+
 #### Marenostrum path
 
 Type the path on Marenostrum GPFS where the testsuite will be executed and the data generated. If the path does not exists, it will be created. By default, the path is `/gpfs/projects/bsc21/bscxxxxx/ts/name_of_your_machine`
@@ -133,7 +141,8 @@ Here, you can define the test subsets you want to run. Type the names of the sub
 
 If you want to change a particular setting, you can run ./configure using one of these options. Note that you can specify an option argument directly in the command line, or let it empty to enable the interactive mode.
 
-*  `-a  | --all                          ` Configure all the options
+*  `-a  | --all                          ` Configure the main options
+*  `-A  | --ALL                          ` Configure all the options
 *  `-e  | --email           [email]      ` Change the email
 *  `-s  | --tests-git-ssh   [git-adress] ` Set up the tests git repository (ssh url)
 *  `-h  | --tests-git-https [git-adress] ` Set up the tests git repository (https url)