The directive initially displays the build status indicating success, failure or in-progress. Adjacent to this is a clickable icon1 that goes back to the server and retrieve the build result statistics and displays them on the screen.
The journey to get here is challenging (especially for someone who works at the back office) but very fulfilling except for one last thing - unit testing.
Below is the directive code:
angular.module('elwoodUiApp')
.constant('BuildResultStatsUrl', 'http://localhost:8080/buildResultStats/:key/:count')
.factory('BuildResultStatsResource', function($resource, BuildResultStatsUrl) {
return $resource(BuildResultStatsUrl, {}, {
'get': {method: 'GET'}
});
})
.directive('elwBuildResultStats', function() {
var controller = function($scope, BuildResultStatsResource, ToKeyCount) {
$scope.toggle = false;
$scope.getBuildResultStats = function(keyCount) {
BuildResultStatsResource.get({'key': keyCount.key, 'count': keyCount.count},
function (successResult) {
console.log(successResult);
if (!$scope.buildResultStats) {
$scope.buildResultStats = [];
$scope.buildResultStats[ToKeyCount(keyCount)] = {
'successCount': successResult.successCount,
'failedCount': successResult.failedCount,
'ignoredCount': successResult.ignoredCount
};
}
$scope.toggle = !$scope.toggle;
}, function (errorResult) {
console.log(errorResult);
}
);
};
$scope.isShowBuildResultStats = function(keyCount) {
return $scope.toggle
&& ($scope.buildResultStats
&& ($scope.status == 'SUCCEEDED' || $scope.status === 'FAILED'));
}
};
return {
restrict: 'A',
templateUrl: 'views/buildresultstats.html',
controller: controller,
scope: {
status: '@',
keyCount: '=',
}
};
});
And below is the test code:
describe('Controller: BuildResultStatsCtrl', function () {
// load the controller's module
beforeEach(module('elwoodUiApp'));
var
scope,
httpBackend;
describe('BuildResultStatsCtrl', function() {
var BuildResultStatsCtrl,
buildResultStatsResource,
toKeyCount;
// Initialize the controller and a mock scope
beforeEach(inject(function ($controller, $rootScope, $compile, $httpBackend, BuildResultStatsResource, ToKeyCount) {
scope = $rootScope.$new();
httpBackend = $httpBackend;
buildResultStatsResource = BuildResultStatsResource;
toKeyCount = ToKeyCount;
var elem = '<div elw-build-result-stats="" key-count="keyCountTuple" status="{{buildStatus}}"></div>';
scope.status = 'SUCCEEDED';
scope.keyCount = {
key: 'PRJ',
count: '10'
};
httpBackend.whenGET('views/buildresultstats.html').respond(200, '');
var template = $compile(elem)(scope, buildResultStatsResource, toKeyCount);
console.log(template);
scope.$digest();
}));
it('should display when status is SUCCEEDED', function() {
var url = 'http://localhost:8080/buildResultStats/PRJ/10';
expect(scope).toBeDefined();
expect(scope.toggle).toBeFalsy();
expect(scope.isShowBuildResultStats).toBeFalsy();
expect(scope.buildResultStats).toBeUndefined();
var mockData = {
successCount: 10,
failedCount: 3,
ignoredCount: 2
};
httpBackend.expectGET(url).respond(mockData);
expect(buildResultStatsResource).toBeDefined();
scope.getBuildResultStats(scope.keyCount);
httpBackend.flush();
expect(scope.toggle).toBeTruthy();
});
});
});
After compiling the element at line number 30, I'm expecting the scope variables and functions will be fully defined and by the time I invoke "scope.getBuildResultStats(scope.keyCount)" the mocked GET should return the mock data.
Well, it looks like it didn't materialise for some unknown reason.
It's almost quarter past 2 in the morning.
Changes aren't committed yet.
I feel very tired but I think I'm almost there...
Update: (2016-02-23 12:10 AM) Extracting the directive's function into a full blown controller and referring the controller with a controller name might be an option. This allows me to test the controller as an standalone component outside of this directive.
.controller('BuildResultStatsCtrl', function($scope, BuildResultStatsResource, ToKeyCount) {
// ...
}
return { restrict: 'A', templateUrl: 'views/buildresultstats.html', controller: 'BuildResultStatsCtrl', scope: { status: '@', keyCount: '=', } };
1Generated from http://www.amp-what.com and I find this website very cool.
