mediawiki-extensions-Popups/tests/node-qunit/processLinks.test.js

116 lines
3.3 KiB
JavaScript
Raw Normal View History

var mock = require( 'mock-require' ),
processLinks = require( '../../src/processLinks' );
/* global Map */
QUnit.module( 'ext.popups/processLinks', {
beforeEach: function() {
this.getTitle = this.sandbox.stub().throws( 'UNIMPLEMENTED' );
mock( '../../src/getTitle', this.getTitle );
processLinks = mock.reRequire( '../../src/processLinks' );
this.$container = $( '<div />' );
this.$container.html(
'<a href="link" title="title" class="blacklisted">Skip this link</a>'
);
this.config = new Map();
window.mediaWiki.Title = {
newFromText: this.sandbox.stub().throws( 'UNIMPLEMENTED' )
};
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
},
afterEach: function() {
mock.stop( '../../src/getTitle' );
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
window.mediaWiki.Title = null;
}
} );
QUnit.test( 'it should not return links without a href attribute', function( assert ) {
this.$container.html(
'<a title="title" class="blacklisted">Skip this link</a>'
);
assert.deepEqual(
processLinks( this.$container, [], this.config ).length,
0
);
} );
QUnit.test( 'it should not return links without a title attribute', function( assert ) {
this.$container.html(
'<a href="link" class="blacklisted">Skip this link</a>'
);
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
assert.deepEqual(
processLinks( this.$container, [], this.config ).length,
0
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
);
} );
QUnit.test( 'it should not return links in the blacklist', function( assert ) {
assert.deepEqual(
processLinks( this.$container, [ '.blacklisted' ], this.config ).length,
0
);
} );
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
QUnit.test( 'it should not return links without valid page title', function( assert ) {
this.getTitle.withArgs( 'link', this.config ).returns( null );
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
assert.deepEqual(
processLinks( this.$container, [], this.config ).length,
0
);
assert.equal( this.getTitle.callCount, 1 );
assert.deepEqual( this.getTitle.getCall( 0 ).args, [ 'link', this.config ] );
} );
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
QUnit.test( 'it should not return links without valid mediawiki title', function( assert ) {
this.getTitle.withArgs( 'link', this.config ).returns( 'title' );
window.mediaWiki.Title.newFromText.withArgs( 'title' ).returns( null );
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
assert.deepEqual(
processLinks( this.$container, [], this.config ).length,
0
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
);
assert.equal( window.mediaWiki.Title.newFromText.callCount, 1 );
assert.deepEqual( window.mediaWiki.Title.newFromText.getCall( 0 ).args, [ 'title' ] );
} );
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
QUnit.test( 'it should not return links without valid namespace', function( assert ) {
this.getTitle.withArgs( 'link', this.config ).returns( 'title' );
window.mediaWiki.Title.newFromText.withArgs( 'title' ).returns( {
namespace: 1
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
} );
// Valid namespaces for content
this.config.set( 'wgContentNamespaces', [ 5 ] );
assert.deepEqual(
processLinks( this.$container, [], this.config ).length,
0
);
} );
QUnit.test( 'it should return only valid links', function( assert ) {
// Valid link
this.getTitle.withArgs( 'link', this.config ).returns( 'title' );
window.mediaWiki.Title.newFromText.withArgs( 'title' ).returns( {
namespace: 5
} );
// Invalid link because of namespace
this.$container.add( '<a href="link2" title="title">Banana</a>' );
this.getTitle.withArgs( 'link2', this.config ).returns( 'title2' );
window.mediaWiki.Title.newFromText.withArgs( 'title2' ).returns( {
namespace: 3 // Not content
} );
// Valid namespaces for content
this.config.set( 'wgContentNamespaces', [ 5 ] );
assert.deepEqual(
processLinks( this.$container, [], this.config ).length,
1
);
Tests: Migrate processLinks.test.js to node-qunit Tests are basically unchanged, except for some stubs on beforeEach. Supporting changes: * Bring stubs from the mediawiki library for mw.Uri, mw.Title.newFromText and mw.RegExp into stubs.js * Remove hook onResourceLoaderTestModules given there are no resource loader test modules after migrating processLinks.test.js Why bring stubs from real source? This is not optimal. It could be the case that the stubs would need to be updated at some point in the future. That's why in the comment of each stub, it is specified where it came from, and what was changed to make it work. It is not optimal but it should help with a future update if necessary. Also checked the history of the stubs and these three stubs are very stable with a small commits per year, usually adding some extra functionality (not breaking changes) (the rest of the commits are docs/format stuff), so the core behavior that we rely on here shouldn't change in a fundamental way. See the github links: * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Uri.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.Title.js * https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki/mediawiki.RegExp.js Right now this stubs allow us to bring the test to run in isolation in node. The initial plan was to do change the test to be less test-case oriented with dependencies on mediawiki.*.js and not to bring fake "real" stubs, but after looking into it, given that: 1. the test cases in the test seem pretty informative showing the kind of links that popups accepts 2. the stubs are acceptably easy to bring in, and are pretty stable I decided to go with this approach initially to finish the migration without changing the meaning of the tests. If we want to remove the stubs and morph the test to verify stub calls and move the test cases to documentation on the source, I'll tackle that on a future commit. Bug: T160406 Change-Id: Ieea378c9b7fec9116222b4a099c226d1f1131f65
2017-04-25 11:58:41 +00:00
} );