-
Notifications
You must be signed in to change notification settings - Fork 1
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
Cannot write HTML reports: Crash error (strongly-named assemblies) #141
Comments
I think that this might be caused by the There's a method:
I think that this needs to be returning the assembly full names instead of their simple names. Now that the assemblies are strongly-named, they won't load properly with just simple names. |
In fact, I can reproduce this if I remove the ZPT-Sharp configuration from the Maybe ZPT-Sharp is 'spinning up' another config instance which is using the configuration file instead of my hard-coded config source. |
WorkaroundPlace the following config into your test project's App.config: <configSections>
<sectionGroup name="CSF">
<sectionGroup name="Zpt">
<section name="PluginConfigurationSection"
type="CSF.Zpt.PluginConfigurationSection, CSF.Zpt, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
<sectionGroup name="ExpressionEvaluators">
<sectionGroup name="CSharpExpressions">
<section name="ExpressionConfigurationSection"
type="CSF.Zpt.ExpressionEvaluators.CSharpExpressions.ExpressionConfigurationSection, CSF.Zpt.ExpressionEvaluators.CSharpExpressions, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
</sectionGroup>
</sectionGroup>
</sectionGroup>
</sectionGroup>
</configSections>
<CSF>
<Zpt>
<PluginConfigurationSection DefaultHtmlDocumentProvider="CSF.Zpt.DocumentProviders.HtmlZptDocumentProvider"
DefaultXmlDocumentProvider="CSF.Zpt.DocumentProviders.XmlLinqZptDocumentProvider"
DefaultExpressionEvaluator="CSF.Zpt.ExpressionEvaluators.PathExpressions.PathExpressionEvaluator">
<PluginAssemblies>
<Assembly Name="CSF.Zpt.DocumentProviders.XmlLinq, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
<Assembly Name="CSF.Zpt.ExpressionEvaluators.CSharpExpressions, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
<Assembly Name="CSF.Zpt.ExpressionEvaluators.NotExpressions, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
<Assembly Name="CSF.Zpt.ExpressionEvaluators.PathExpressions, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
<Assembly Name="CSF.Zpt.ExpressionEvaluators.StringExpressions, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
<Assembly Name="CSF.Zpt.DocumentProviders.HtmlHAP, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
<Assembly Name="CSF.Zpt.ExpressionEvaluators.LoadExpressions, Version=1.0.6.0, Culture=neutral, PublicKeyToken=83989bab8a1a4730"/>
</PluginAssemblies>
</PluginConfigurationSection>
<ExpressionEvaluators>
<CSharpExpressions>
<ExpressionConfigurationSection>
<Assemblies>
<Assembly Name="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
</Assemblies>
<Namespaces>
<Namespace Name="System"/>
<Namespace Name="System.Linq"/>
</Namespaces>
</ExpressionConfigurationSection>
</CSharpExpressions>
</ExpressionEvaluators>
</Zpt>
</CSF> |
This provides working HTML reports, using the workaround documented at: csf-dev/CSF.Screenplay#141 (comment)
I have had to defer this for now, since it's blocked on an upstream ZPT-Sharp issue. |
This is no longer critical. Because of architectural changes it is now acceptable to keep this in the Wontfix. |
Here's an error I've seen from the Agiil project.
Additionally, at the end of the test run I saw this:
The text was updated successfully, but these errors were encountered: