Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting Error while executing tests using Test Centric GUI #2757

Open
nitkkiran opened this issue Jul 23, 2024 · 1 comment
Open

Getting Error while executing tests using Test Centric GUI #2757

nitkkiran opened this issue Jul 23, 2024 · 1 comment
Labels

Comments

@nitkkiran
Copy link

SpecFlow Version

3.9.74

Which test runner are you using?

NUnit

Test Runner Version Number

TestCentric.GuiRunner 2.0.0-beta4

.NET Implementation

equal or greater .NET Framework 4.6.1

Project Format of the SpecFlow project

Classic project format using <PackageReference> tags

.feature.cs files are generated using

SpecFlow.Tools.MsBuild.Generation NuGet package

Test Execution Method

TFS/VSTS/Azure DevOps – Task – PLEASE SPECIFY THE NAME OF THE TASK

SpecFlow Section in app.config or content of specflow.json

{
"specFlow": {
"unitTestProvider": {
"name": "nunit"
}
}
}

Issue Description

I am trying to run Nunit Specflow Tests using TestCentric GUI, I can load the test dll but when I run the test, I get the following error
OneTimeSetup:Bodi.ObjectContainerException : Interface cannot be resolved: TechTalk.SpecFlow.UnitTestProvider.IUnitTestRuntimeProvider('nunit')

I am using .NET Framework 4.8 with the following nuget packages

SpecFlow 3.9.74
SpecFlow.NUnit 3.9.74
NUnit 4.1.0
NUnit3testAdapter 4.5.0
Test Centric Error

Steps to Reproduce

Execute Test using TestCentric GUI tool
Test Centric Error

Link to Repro Project

No response

@nitkkiran nitkkiran added the Bug label Jul 23, 2024
@DeLaphante
Copy link

I would advised all to not use Specflow+ Runner or LivingDoc as its currently not being supported or developed - migrate to MsTest or Nunit and also update to latest .net 8+ and use third party reporting libraries such as extent report.

Specflow is working perfectly fine for me with the above changes in the following daily github actions repo -> https://github.com/DeLaphante/CynkyAutomation/actions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants