fescobar / allure-docker-service

This docker container allows you to see up to date reports simply mounting your "allure-results" directory in the container (for a Single Project) or your "projects" directory (for Multiple Projects). Every time appears new results (generated for your tests), Allure Docker Service will detect those changes and it will generate a new report automatically (optional: send results / generate report through API), what you will see refreshing your browser.
Apache License 2.0
640 stars 183 forks source link

container showing skipped tests as failed #152

Closed khanzzirfan closed 3 years ago

khanzzirfan commented 3 years ago

Tests ran successfully with few of the tests removed and skipped. The removed tests were failed in the previous run. The current results in docker container reporting showing the removed tests as failed. Anyidea how to fix this? or is this a bug?

Also the test counts is also wrong. It should be 10 total test cases but the results are showing 13. Please see below results summary.

Current report run image

And these are the test result files posted to Allure docker service container.

  <ResultSummary outcome="Completed">
    <Counters total="10" executed="10" passed="10" failed="0" error="0" timeout="0" aborted="0" inconclusive="0" passedButRunAborted="0" notRunnable="0" notExecuted="0" disconnected="0" warning="0" completed="0" inProgress="0" pending="0" />
    <Output>
      <StdOut>The following test cases were skipped because they do not match the specified filter: LoginScenarios, LoginScreen, OpsManagerDashboard, SelectFlight-ValidateAllAirports, FindBooking - User should be search bookings for a specific transaction, FindBooking - see all default filter options, FindBooking - Searchbooking for a one month, FindBooking- Search with more filters, FindBooking- Search booking by name, FindBooking - See all default booking filter options, CreateScheduleBookingCash, CreateScheduleBookingCCPayment - SuccessScenario, CreateScheduleBookingCCPayment - UnsuccessfulScenario, create quick freight complete booking, view quick freight booking, Evtprodu anchorage freight search , EvtProdu dashboard screen validation, EvtProdu CreateQuickFreight-Validatefields, EvtProdu Tag flight should throw error when no tags available, EvtProdu CreateNew Tags, EvtProdu Assign tag to scheduled booking flight&#xD;
Starting the create quick freight test...&#xD;
Starting the create quick freight mandatory office selection test...&#xD;
Starting the validate add freight mandatory fields test...&#xD;
Starting the Validate add freight window fields test...&#xD;
Starting the search by freights by agent test...&#xD;
Starting the freights from kotlik to emmonak test...&#xD;
Starting the Search all freights from Kotlik test...&#xD;
Starting the DashboardScreenValidation test...&#xD;
Starting the create new tags test...&#xD;
Starting the assign tag to scheduled booking flight_1 test...&#xD;
</StdOut>
    </Output>
  </ResultSummary>
</TestRun>
fescobar commented 3 years ago

@khanzzirfan what is your configuration? maybe this can help you https://github.com/fescobar/allure-docker-service/issues/145#issuecomment-776019243

khanzzirfan commented 3 years ago

Here is the configuration Azure Yaml template


{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "containerGroups_tst_tf_allure_report_api_aci_name": {
      "defaultValue": "tst-tf-allure-report-api-aci",
      "type": "String"
    }
  },
  "variables": {},
  "resources": [
    {
      "type": "Microsoft.ContainerInstance/containerGroups",
      "apiVersion": "2019-12-01",
      "name": "[parameters('containerGroups_tst_tf_allure_report_api_aci_name')]",
      "location": "[resourceGroup().location]",
      "properties": {
        "sku": "Standard",
        "containers": [
          {
            "name": "[parameters('containerGroups_tst_tf_allure_report_api_aci_name')]",
            "properties": {
              "image": "frankescobar/allure-docker-service",
              "ports": [
                {
                  "protocol": "TCP",
                  "port": 5050
                }
              ],
              "volumeMounts": [
                {
                  "name": "filesharevolume",
                  "mountPath": "/app/projects"
                }
              ],
              "environmentVariables": [
                {
                  "name": "CHECK_RESULTS_EVERY_SECONDS",
                  "value": 1
                },
                {
                  "name": "KEEP_HISTORY",
                  "value": 1
                },
                {
                  "name": "KEEP_HISTORY_LATEST",
                  "value": 25
                }
              ],
              "resources": {
                "requests": {
                  "memoryInGB": 1,
                  "cpu": 1
                }
              }
            }
          }
        ],
        "initContainers": [],
        "restartPolicy": "OnFailure",
        "osType": "Linux",
        "ipAddress": {
          "ports": [
            {
              "protocol": "TCP",
              "port": 5050
            }
          ],
          "type": "Public"
        },
        "volumes": [
          {
            "name": "filesharevolume",
            "azureFile": {
              "shareName": "zzzsharetflite",
              "storageAccountName": "zzzzinternal",
              "storageAccountKey": "zzzzzzzzzzzzzzzzzzzzzzzzzzzzz=="
            }
          }
        ]
      }
    }
  ]
}
fescobar commented 3 years ago

@khanzzirfan in this case. I recommend you disable the automatic check results and use the api to clean results, send results and generate reports.

khanzzirfan commented 3 years ago

Seems its working now. Thanks @fescobar . Much appreciated.