.gitlab-ci.yml

# You can override the included template(s) by including variable overrides
# SAST customization: https://docs.gitlab.com/ee/user/application_security/sast/#customizing-the-sast-settings
# Secret Detection customization: https://docs.gitlab.com/ee/user/application_security/secret_detection/#customizing-settings
# Dependency Scanning customization: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#customizing-the-dependency-scanning-settings
# Note that environment variables can be set in several places
# See https://docs.gitlab.com/ee/ci/variables/#cicd-variable-precedence
image: trikiller/selenium_net5:v3

#variables:
#    ALLURE_LAUNCH_NAME: "${CI_PROJECT_NAME} - ${CI_COMMIT_SHORT_SHA}" #mandatory
#    ALLURE_LAUNCH_TAGS: "regular, ${CI_COMMIT_REF_NAME}" #mandatory
#    ALLURE_TESTPLAN_PATH: "testplan.json" #mandatory
#    ALLURE_RESULTS: "allure-results" #mandatory

stages:
  - run-nunit

run-nunit:
    stage: run-nunit
    
    script:
        - dotnet restore
        - dotnet run --project SpecFlowAllure/SpecFlowAllure.csproj
    artifacts:
        when: always
        paths:
            - allure-results/        
    allow_failure: true