Remove nested .git from TestCases/TestCases and add nested preconditioner test scripts

Author: eorbay-metu

TestCases/TestCases

@@ -0,0 +1,66 @@
+# Continous Integration setup for SU2.
+# Tests with the SU2 develop branch when the TestCases repository is modified.
+
+language: cpp
+
+compiler:
+    - g++
+
+notifications:
+    email:
+        recipients:
+            - [email protected]
+  
+branches:
+    only:
+        - develop
+
+env:
+    global:
+        CXXFLAGS=-O3
+        BUILD_DIR=$TRAVIS_BUILD_DIR/SU2
+    matrix:
+        # Serial build and test
+        - CONFIGURE_COMMAND="./configure --prefix=$BUILD_DIR --enable-PY_WRAPPER"
+          TEST_SCRIPT=serial_regression.py
+        # Parallel build and test
+        - CONFIGURE_COMMAND="./configure --enable-mpi --with-cc=mpicc --with-cxx=mpicxx --prefix=$BUILD_DIR --enable-PY_WRAPPER"
+          TEST_SCRIPT=parallel_regression.py
+
+before_install:
+    # install the necessary packages
+    - sudo apt-get update -qq
+    - sudo apt-get install -qq python-numpy python-scipy python-pip mpich2 swig
+    # Move all of the test data for easier copying into the SU2 repo
+    - mkdir TestData
+    - shopt -s extglob
+    - mv -- !(TestData) TestData
+    # Get the code
+    - git clone https://github.com/su2code/SU2.git
+    - cd SU2
+    - git checkout develop
+
+install:
+    - sudo pip install mpi4py
+    - echo $BUILD_DIR
+    - echo $CONFIGURE_COMMAND
+    - $CONFIGURE_COMMAND
+    - make -j 4
+    - make install
+    
+    # Add environmental variables according to the configure step
+    - export SU2_RUN=$BUILD_DIR/bin
+    - export SU2_HOME=$BUILD_DIR
+    - export PATH=$PATH:$SU2_RUN
+    - export PYTHONPATH=$PYTHONPATH:$SU2_RUN
+
+before_script:
+    # Copy the test case data from above into the folder structure
+    - cp -R ../TestData/* ./TestCases/
+    # Enter the SU2/TestCases/ directory, which is now ready to run
+    - cd TestCases/
+
+script:
+    # run the tests
+    python $TEST_SCRIPT
+

TestCases/TestCases/.travis.yml

@@ -0,0 +1,23 @@
+--------------------------------
+  SU2: The Open-Source CFD Code
+--------------------------------
+
+Computational analysis tools have revolutionized the way we design aerospace systems, but most established codes are proprietary, unavailable, or prohibitively expensive for many users. The SU2 team is changing this, making computational analysis and design freely available as open-source software and involving everyone in its creation and development.
+
+-----------------------------------------------------------
+  SU2 TEST CASES
+-----------------------------------------------------------
+
+SU2 provides an extensive collection of common test cases. The test cases contain meshes and configuration files that can be run to ensure different components of the suite are working properly. The directory structure is organized by governing equations and their specific cases.
+
+The files found within these directories serve two purposes:
+
+1. A subset of the available cases are used for regression testing internally by the development team. The configuration files and meshes are automatically downloaded and executed with the latest version of SU2 at regular intervals. Any changes in the output of the specified test cases are immediately reported to the developers. These cases are controlled by the Python scripts in the root of the test cases directory, e.g., serial_regression.py.
+
+2. The entire suite of test cases is provided to the community as a way to get started with SU2 and its many configuration options, including settings that the developers consider to be good starting points. Often, you will find a test case that is similar to your problem of interest, and the available configuration files can be modified to suit your needs.
+
+Note that, while many of the cases are used for regression testing, this test case suite is provided **without any guarantees on performance or expected results** (check out the [tutorials](https://su2code.github.io/tutorials/home/) for more thoroughly maintained cases). Keep in mind that small changes to the configuration options can often result in large changes to the output. We encourage the community to experiment with these test cases, or even try (and share!) other interesting validation cases with SU2! 
+
+Happy testing!
+
+- The SU2 Development Team