reportportal / agent-net-specflow

Report Portal agent for SpecFlow
Apache License 2.0
10 stars 4 forks source link

Specflow agent 1.5.1 and ReportPortal v5 #48

Closed gkalnytskyi closed 4 years ago

gkalnytskyi commented 4 years ago

My company is evaluating ReportPortal and recently upgraded the installation to ReportPortal 5 (beta). The issue at the moment is that I cannot log any data to ReportPortal 5, even though the agent configuration hasn't changed much. Also, no "ReportPortal.log" file is created when I run tests to allow me to understand the issue.

Nuget packages:

Config:

{
  "$schema": "https://raw.githubusercontent.com/reportportal/agent-net-specflow/master/ReportPortal.SpecFlowPlugin/ReportPortal.config.schema",
  "enabled": true,
  "server": {
    "url": "${server uri}:8080/api/v1/",
    "project": "project_blah",
    "authentication": {
      "uuid": "5d655790-8084-4a61-afe0-b3096d01fe4e"
    }
  },
  "launch": {
    "name": "launch_name",
    "description": "acceptance_tests",
    "debugMode": true,
    "tags": []
  }
}
nvborisenko commented 4 years ago

Known issue in beta https://github.com/reportportal/reportportal/issues/684

gkalnytskyi commented 4 years ago

And what about the absence of ReportPortal.log file?

nvborisenko commented 4 years ago

It might be issue, but I guess issue is in nuget packages. I see you installed the latest Shared package, while RP.SpecFlow is still old. Please resolve dependencies. Example: RP.SpecFlow v1.5.1 requires Shared v2.1.4, which requires RP.Client 2.1.8. Please try these exact versions.

Actually we didn't introduce constraints in nuget packages. Your case is good to think about it.

gkalnytskyi commented 4 years ago

Hello @nvborisenko , I have downgraded the packages and reran the tests, and still no ReportPortal.log file was generated.

nvborisenko commented 4 years ago

Please prepare simple test project to reproduce the issue. It will be very useful in figuring out what is wrong.

nvborisenko commented 4 years ago

@gkalnytskyi, closing it due inactivity, feel free to reopen if the issue is still reproducible.