[Mono-bugs] [Bug 694096] New: ArgumentNullException when FireEvents is true

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=694096

https://bugzilla.novell.com/show_bug.cgi?id=694096#c0


           Summary: ArgumentNullException when FireEvents is true
    Classification: Mono
           Product: Mono: Tools
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Gendarme
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: stuken.yuri at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.30
(KHTML, like Gecko) Chrome/12.0.742.53 Safari/534.30

If there is a test case with FireEvents set to true, and this test case reports
a defect, it may fail with ArgumentNullException thrown in
Gendarme.Framework.Defect::.ctor.
There are some other related problems. When FireEvents is true, rule actually
executes twice, first time when OnMethod/OnType/OnAssembly called in
Test.Rules.Fixtures.RuleTestFixture::RunRule and second time (if no exception
was thrown yet) few line later, when runner.CheckMethod is called.
Furthermore, there are obvious typos in the same method when events are fired
on types and assemblies: md and td objects are used while td and ad should be
used respectively.

Reproducible: Always

Steps to Reproduce:
1. Run
Test.Rules.Exceptions.DoNotThrowInUnexpectedLocationTest::EqualityOperator test
case. It is important to run a test case alone, because test cases executed
previously may modify runner's state so that no exception will be thrown (I
guess that's why it wasn't fixed yet).
Actual Results:  
Test.Rules.Exceptions.DoNotThrowInUnexpectedLocationTest.EqualityOperator:
System.ArgumentNullException : Value cannot be null.
Parameter name: target

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.