Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I INMOST
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Terekhov
  • INMOST
  • Wiki
  • 5002 Prepearing test

5002 Prepearing test · Changes

Page history
Updated 5001 Prepearing test (markdown) authored Jan 16, 2015 by Kirill Terekhov's avatar Kirill Terekhov
Hide whitespace changes
Inline Side-by-side
5002-Prepearing-test.md 0 → 100644
View page @ d7010831
Prepearing test for INMOST
=====
This page will guide you through how you can prepear test for INMOST.
##Naming test.
Following naming convention should be used for tests:
* tests for Domain - domain_test000-domain_test999
* test for Mesh - mesh_test000-mesh_test999
* test for Mesh in parallel - pmesh_test000-pmesh_test999
* test for Solver - solver_test000-solver_test999
* test for Autodiff - autodiff_test000-autodiff_test999
* tests for Nonlinear Solver - nonlinear_test000-nonlinear_test999
You should create folder with your name in Tests folder. Use this folder for your tests source and data.
##Prepearing for CMake.
First open Tests/CMakeLists.txt file and add a line "add_subdirectory(your_test_name)"
In folder of your test create CMakeLists file as well.
To be continued...
###Using additional resource files in tests
To be continued...
##Describing test in WIKI
When you have finished tuning and setting your tests, it is recommended that you create an article describing test in Wiki.
Use following name for a new article on Wiki.
First you should get unique 4-digit number in accordance with:
* for Domain tests 5100-5199
* for Mesh tests 5200-5299
* for parallel Mesh tests 5300-5399
* for Solver tests 5400-5499
* for Autodiff tests 5500-5599
* for Nonlinear Solver tests 5600-5699
Then append to this number several short keywords that describe the test. Separate 4-digit number and keywords with spaces. Look into other articles for contents.
Clone repository
  • 0100 Compilation
  • 0200 Compilation Windows
  • 0201 Obtain MSVC
  • 0202 Obtain MSMPI
  • 0203 Compilation INMOST Windows
  • 0204 Compilation ParMETIS Windows
  • 0205 Compilation Zoltan Windows
  • 0206 Compilation PETSc Windows
  • 0207 Compilation Trilinos Windows
  • 0400 Compilation Linux
  • 0401 Install MPI
  • 0402 Compilation INMOST Linux
  • 0403 Compilation PETSc Linux
  • 0404 Compilation Trilinos Linux
  • 0405 Compilation ParMETIS Linux
View All Pages