-
Notifications
You must be signed in to change notification settings - Fork 65
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
Allure.XUnit.AllureXunitFacade failure: Could not load type 'System.Web.IHttpModule' from assembly System.Web #412
Comments
Hi, @pauuser ! You may disable the feature in allureConfig.json:
That should prevent allure from scanning the assemblies and the error should disappear. See more info here. |
Now, it only considers assemblies with names matching the *reporters* pattern.
Now, it only considers assemblies with names matching the *reporters* pattern.
Now, it only considers assemblies with names matching the *reporters* pattern.
Now, it only considers assemblies with names matching the *reporters* pattern.
Now, it only considers assemblies with names matching the *reporters* pattern.
Now, it only considers assemblies with names matching the *reporters* pattern.
* Use common failed/broken algorithm by allure-xunit * Remove obsolete allure-xunit's example * Remove false warning for skipped theories (#421) * Use the common skip reason for test plans * Remove separate project for xunit reporter * Consolidate Allure.Xunit under single namespace * Remove obsolete API from Allure.Xunit - using-style steps/fixtures: - Allure.Xunit.AllureBefore - Allure.Xunit.AllureAfter - Allure.Xunit.AllureStep - Allure.Xunit.AllureStepBase - Async attachment functions in Allure.Xunit.AllureAttachments - Unused internal methods of AllureXunitHelper that had accidentally leaked into public API: - StartTestContainer - StartTestCase - MarkTestCaseAsFailedOrBroken - MarkTestCaseAsPassed - MarkTestCaseAsSkipped - FinishTestCase - The Allure.Xunit.Steps class - AllureXunitAttribute and AllureXunitTheoryAttribute (not used anymore) * Fix allure-xunit README * Make internal API hidden from public * Make second reporter resolution more strict (#412) Now, it only considers assemblies with names matching the *reporters* pattern. * Set Allure.Xunit's TFMs to netstandard2.0 and netcoreapp3.1 * Remove redundant code from AllureXunitHelper * Ensure proper casing at Allure.Xunit fs names
Allure.Xunit 2.12.0 is more restrictive on what assemblies it considers when scanning for the second reporter. Issues like this one should now appear much less frequently. |
I'm submitting a ...
What is the current behavior?
Running an XUnit test project in Gitlab runner docker, I get the following runtime exception:
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
To reproduce this issue I am providing you with my gitlab CI configuration:
Here is my csproj file. I am using .NET 7 and XUnit.Allure 2.10.0
What is the expected behavior?
Normally the test project should not fail. If I remove the Allure package, tests pass successfully.
What is the motivation / use case for changing the behavior?
Test project does not work because of the Allure package.
Please tell us about your environment:
Other information
I have an impression that the package uses a .NET framework library which cannot be found and used in .NET Core applications.
The text was updated successfully, but these errors were encountered: