1
0
Fork 0
easejs/test/Trait/VirtualTest.js

187 lines
5.1 KiB
JavaScript
Raw Normal View History

/**
* Tests virtual trait methods
*
* Copyright (C) 2014 Mike Gerwitz
*
* This file is part of GNU ease.js.
*
* ease.js is free software: you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation, either version 3 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
require( 'common' ).testCase(
{
caseSetUp: function()
{
this.Sut = this.require( 'Trait' );
this.Class = this.require( 'class' );
},
/**
* If a trait specifies a virtual method, then the class should expose
* the method as virtual.
*/
'Class inherits virtual trait method': function()
{
var expected = 'foobar';
var T = this.Sut(
{
'virtual foo': function()
{
return expected;
}
} );
var C = this.Class.use( T ).extend( {} );
// ensure that we are actually using the method
this.assertEqual( C().foo(), expected );
// if virtual, we should be able to override it
var expected2 = 'foobaz',
C2;
this.assertDoesNotThrow( function()
{
C2 = C.extend(
{
'override foo': function()
{
return expected2;
}
} );
} );
this.assertEqual( C2().foo(), expected2 );
},
/**
* Virtual trait methods should be treated in a manner similar to
* abstract trait methods---a class should be able to provide its own
* concrete implementation. Note that this differs from the above test
* because we are overriding the method internally at definition time,
* not subclassing.
*/
'Class can override virtual trait method': function()
{
var _self = this;
var T = this.Sut(
{
'virtual foo': function()
{
// we should never execute this (unless we're broken)
_self.fail( true, false,
"Method was not overridden."
);
}
} );
var expected = 'foobar';
var C = this.Class.use( T ).extend(
{
'override foo': function() { return expected; }
} );
this.assertEqual( C().foo(), expected );
},
/**
* If C uses T and overrides T.Ma, and there is some method T.Mb that
* invokes T.Ma, then T.Mb should instead invoke C.Ma.
*/
'Class-overridden virtual trait method is accessible by trait':
function()
{
var _self = this;
var T = this.Sut(
{
'public doFoo': function()
{
// should call overridden, not the one below
this.foo();
},
// to be overridden
'virtual protected foo': function()
{
_self.fail( true, false, "Method not overridden." );
},
} );
var called = false;
var C = this.Class.use( T ).extend(
{
// should be called by T.doFoo
'override protected foo': function() { called = true },
} );
C().doFoo();
this.assertOk( called );
},
/**
* If a supertype mixes in a trait that provides a virtual method, a
* subtype should be able to provide its own concrete implementation.
* This is especially important to test in the case where a trait
* invokes its own virtual method---we must ensure that the message is
* properly passed to the subtype's override.
*
* For a more formal description of a similar matter, see the
* AbstractTest case; indeed, we're trying to mimic the same behavior
* that we'd expect with abstract methods.
*/
'Subtype can override virtual method of trait mixed into supertype':
function()
{
var _self = this;
var T = this.Sut(
{
'public doFoo': function()
{
// this call should be passed to any overrides
return this.foo();
},
// this is the one we'll try to override
'virtual protected foo': function()
{
_self.fail( true, false, "Method not overridden." );
},
} );
var called = false;
// C is a subtype of a class that implements T
var C = this.Class.use( T ).extend( {} )
.extend(
{
// this should be called instead of T.foo
'override protected foo': function()
{
called = true;
},
} );
C().doFoo();
this.assertOk( called );
},
} );