Skip to content
Snippets Groups Projects

F local inttests

Merged Florian Spreckelsen requested to merge f-local-inttests into dev

Summary

For https://gitlab.indiscale.com/caosdb/customers/f-fit/management/-/issues/40. Introduces a server-profile that can be used to run the integration tests locally and adds documentation. Depends on the new debug_authtoken_dir profile variable from the corresponding Linkahead branch for the authtoken tests.

Focus

Does the new profile work for you?

Test Environment

Follow the new documentation in the f-local-inttests branch of linkahead. Configure the int test setup with the new test profile accordingly and run the tests. All should pass.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

  • All automated tests pass
  • Reference related issues
  • Up-to-date CHANGELOG.md (or not necessary)
  • Up-to-date JSON schema (or not necessary)
  • Appropriate user and developer documentation (or not necessary)
    • How do I use the software? Assume "stupid" users.
    • How do I develop or debug the software? Assume novice developers.
  • Annotations in code (Gitlab comments)
    • Intent of new code
    • Problems with old code
    • Why this implementation?

Check List for the Reviewer

  • I understand the intent of this MR
  • All automated tests pass
  • Up-to-date CHANGELOG.md (or not necessary)
  • Appropriate user and developer documentation (or not necessary)
  • The test environment setup works and the intended behavior is reproducible in the test environment
  • In-code documentation and comments are up-to-date.
  • Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

Edited by I. Nüske

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Florian Spreckelsen marked this merge request as draft

    marked this merge request as draft

  • Bei mir laufen (mit evtl. etwas abgeändertem Setup) die foldenden Tests durch / nicht durch:

    tests/test_administration.py ..................................................
    tests/test_affiliation.py .................s
    tests/test_authentication.py s......FFFFF
    tests/test_boolean.py ...
    tests/test_creation.py .
    tests/test_data_model_leap.py .
    tests/test_datatype.py ...........
    tests/test_datatype_inheritance.py ....x...
    tests/test_datetime.py ..........
    tests/test_deletion.py ..
    tests/test_double.py .
    tests/test_empty_text_value.py ....xx
    tests/test_error_stuff.py ..x.........
    tests/test_file.py ...............
    tests/test_importance.py ......
    tests/test_inheritance.py ......
    tests/test_issues_mysqlbackend.py ..
    tests/test_issues_pylib.py ..
    tests/test_issues_server.py .x......................x..x..xx....................x..xxxxxxxxxxxxx
    tests/test_list.py ...............................
    tests/test_manual.py ..s
    tests/test_messages.py ..
    tests/test_misc.py ...................
    tests/test_name_properties.py ..............x
    tests/test_parents.py x
    tests/test_permissions.py .x...................................
    tests/test_plantuml.py ...
    tests/test_properties.py .
    tests/test_pylib_caching.py ..
    tests/test_query.py ...............x..........x..
    tests/test_query_template.py .....................
    tests/test_query_version.py .x....................xxx
    tests/test_records.py .....s.
    tests/test_recordtypes.py ..
    tests/test_recursive_parents.py ...
    tests/test_reference_xml.py .
    tests/test_select.py ..........................xx..
    tests/test_server_side_scripting.py ....FFFFF..F
    tests/test_state.py ..................x.x
    tests/test_tenpoints.py .........
    tests/test_tickets.py ................s...................
    tests/test_tickets_200.py ....................
    tests/test_tickets_300.py .
    tests/test_unit.py .......
    tests/test_update.py ...x
    tests/test_version.py ........xxxxxx............
    tests/test_xmlparsing.py . 
    
    11 failed, 544 passed, 5 skipped, 43 xfailed, 3061 warnings
    Edited by I. Nüske
  • added 12 commits

    Compare with previous version

  • added 3 commits

    • 4c58307f - TST: Adapt setup for authtokens
    • 579bc96b - TST: modernize symlink test
    • d9cca526 - TST: Remove scripting bin dir local option

    Compare with previous version

  • added 1 commit

    • a73f3d31 - PIPELINE: Copy the contents of resources directory

    Compare with previous version

  • added 1 commit

    Compare with previous version

  • Florian Spreckelsen marked this merge request as ready

    marked this merge request as ready

  • Florian Spreckelsen changed the description

    changed the description

27 27 WORKDIR /git
28 28 # wait for server,
29 29 CMD /wait-for-it.sh caosdb-server:10443 -t 500 -- \
30 # ... install pylinkahead.ini the server-side scripts
30 # ... install pylinkahead.ini and the server-side scripts
31 31 cp /git/.docker/sss_pylinkahead.ini /scripting/home/.pylinkahead.ini && \
32 cp -r /git/resources /scripting/bin-debug && \
  • 19 # WEBUI: dev
    20 # ADVANCEDUSERTOOLS: dev
    21
    22 # General configuration options
    23 conf:
    24 # Shall the SQL & caosroot dumps at custom/other/restore/ be used?
    25 # restore: false
    26 restore: true
    27 # Shall the server run in debug mode?
    28 # This will bind-mount the following directories from custom into the Docker
    29 # container:
    30 # - debug-authtoken :: Authentication tokens will be stored here.
    31 # - debug-scripting-bin :: Used as the server-side scripting bin dir.
    32 # debug: false
    33 debug: true
    34 debug_authtoken_dir: "/tmp/linkahead-pyinttest/authtoken/"
  • 535 535 flags={
    536 536 "InsertFilesInDir": path_on_server +
    537 537 "linked_subfolder"})
    538 assert_is_not_none(c.messages["Warning", 6])
    539 assert_equal(c.messages["Warning", 6][0],
    540 "Directory or file is symbolic link: " + path_on_server +
    541 "linked_subfolder")
    538 assert c.messages.get("Warning", 6, exact=True) is not None
  • 45 45
    46 46 _TEST_SCRIPTS = ["not_executable", "ok", "err", "ok_anonymous"]
    47 47
    48 try:
  • 2
    3 1 # README
    4 2
    5 3 ## Welcome
    6 4
    7 This is the **CaosDB Python Integration Testing** repository and a part of the
    8 CaosDB project.
    5 This is the **Linkahead Python Integration Testing** repository and a part of the
    6 Linkahead project.
    9 7
    10 8 ## Getting started #
    11 9
    12 - To run tests, start up a CaosDB server with the following properties (documentation for this can
    10 ### Configuration
    11
    12 The following steps describe how to setup the tests for running agains
  • added 2 commits

    • 41b79c5b - PIPLINE: Remove local scripting bin dir from pylinkahead.ini
    • 705b3fbb - MAINT: Remove Florian's cert symlink

    Compare with previous version

  • Florian Spreckelsen marked the checklist item All automated tests pass as completed

    marked the checklist item All automated tests pass as completed

  • Florian Spreckelsen marked the checklist item Reference related issues as completed

    marked the checklist item Reference related issues as completed

  • Florian Spreckelsen marked the checklist item Up-to-date JSON schema (or not necessary) as completed

    marked the checklist item Up-to-date JSON schema (or not necessary) as completed

  • Florian Spreckelsen marked the checklist item Appropriate user and developer documentation (or not necessary) as completed

    marked the checklist item Appropriate user and developer documentation (or not necessary) as completed

  • Florian Spreckelsen marked the checklist item Annotations in code (Gitlab comments) as completed

    marked the checklist item Annotations in code (Gitlab comments) as completed

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading