The second call to WithViewData throws NullReferenceException
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- testing-qa
Research direction
Start with ViewResultBaseAssertions.WithViewData, using the stack trace and the HelpEditorControllerTest.GetByPageName_Should_return_view_for_specified_pageName test as entry points. Reproduce the chained assertions and verify that successive WithViewData calls, including the final null value, complete without a NullReferenceException.
Written by the indexing model from the issue text.
Description
This code:
const string pageName = "pageName";
_sut.GetByPageName(pageName)
.Should()
.BeViewResult()
.WithViewData("PageName", pageName)
.WithViewData("Roles", _roles) // this call fails!
.WithViewData("FieldName", null);
causes:
System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.
Source=FluentAssertions.Mvc5
StackTrace:
at FluentAssertions.Mvc.ViewResultBaseAssertions`1.WithViewData(String key, Object expectedValue, String reason, Object[] reasonArgs)
at Tests.Controllers.HelpEditor.HelpEditorControllerTest.GetByPageName_Should_return_view_for_specified_pageName() in ...\....Tests\Controllers\HelpEditor\HelpEditorControllerTest.cs:line 48
- Dominant language
- C#
- Stars
- 36
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentassertions/fluentassertions.mvc
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fluentassertions/fluentassertions.mvc#42 · 4 comments ·
-
help wanted
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
help wanted
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in fluentassertions/fluentassertions.mvc
Similar issues
-
untriaged
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/dotnet-api-docs#13095 ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
newrelic/newrelic-dotnet-agent#3850 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
LuckyPennySoftware/AutoMapper#4660 ·