Mocking Properties

[William Madden]

What're the limitations of mocking properties? Does mockolate create getters and setters in its bytecode for public properties that I can stub/mock or are properties just available on the mock as they would be on the real class?

For example,

class A {

  public var a : String;

}

class BTest {

  [Mock]

  public var a : A;

  public var b : B;

  [Before]

  public function beforeEach() : void {

    b = new B();

  }

  [Test]

  public function someTest() : void {

    expect(a.a = "abc"); // Would this work?

    b.someFunc();

    // Or should it be

    assertThat( a.a, equalTo('abc') );

  }

}

[Drew Bourne]

Only getters and setters are mockable, public vars are not. It is an unfortunately limitation of ABC that public variables cannot be override or proxied by public getters and setters in subclasses. 

I am undecided about whether to actively generate warnings for unmockable variables and similar situations. Your thoughts? Would it have helped diagnose your current issue?

cheers, 

Drew

[William Madden]

It's unfortunate, but I suppose it's not that bad.

I don't think warnings from the mock calls (nice(), strict() etc.) are necessary, but I think there should definitely be feedback if you try to create an unsatisfiable expectation, e.g. expect(a.a = "abc"). That would certainly have helped me.

Will