Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteTest an AngularJS directive through the same compilation and linking path the application uses: load its module, compile representative markup with $compile, link it to the expected scope, then assert the DOM, bindings, events, and collaborator calls that form the directive’s public contract. Use angular-mocks.js and ngMock to control framework services, and use $httpBackend with flush() when the directive makes HTTP requests.
What a directive test should prove
A directive is not just a JavaScript function to call in isolation. AngularJS directives are markers on elements, attributes, comments, or classes that the HTML compiler uses to attach behavior or transform an element and its children. A useful unit test therefore starts with the markup a user or template would provide and verifies the observable result.
Define the contract first
- Rendering: expected elements, classes, attributes, or text appear.
- Binding: input values reach the directive and changes are reflected in the DOM.
- Interaction: a click, input, or other event changes state or calls a collaborator.
- Required configuration: attributes, element content, or controller requirements are handled correctly.
- Asynchronous work: a service response eventually produces the promised output.
Assert what the directive promises to its template and users rather than private helper variables or implementation details.
Set up the AngularJS test context
Include the application bundle, the test runner, and angular-mocks.js. The mocks package provides the ngMock module and the familiar module() and inject() helpers. These helpers let a test load the same application module while replacing or controlling services synchronously.
#1 Best Overall
<script src="angular.js"></script>
<script src="angular-mocks.js"></script>
<script src="app.js"></script>
<script src="widget.directive.spec.js"></script>In a Jasmine-style suite, load the module before each test and inject only the services needed by that test:
describe('statusBadge directive', function () {
beforeEach(module('app'));
var $compile, $rootScope;
beforeEach(inject(function (_$compile_, _$rootScope_) {
$compile = _$compile_;
$rootScope = _$rootScope_;
}));
});The exact runner and bundling arrangement depends on the project. The official AngularJS material documents the mechanisms, not one universal runner configuration, so verify the versions and dependency order used by your legacy application.
Compile and link representative markup
$compile matches directives in a template and returns a function that links the compiled result to a scope. Compile the directive in the form the application actually uses, then link it with the scope arrangement defined by the directive.
it('renders the current status', function () {
var scope = $rootScope.$new();
scope.status = 'Ready';
var element = $compile(
'<status-badge value="status"></status-badge>'
)(scope);
scope.$digest();
expect(element.text()).toContain('Ready');
});Match the directive’s scope mode
Use an inherited scope when the directive reads properties from its parent, and provide the attributes and bindings required by an isolated scope. A test that accidentally supplies the wrong scope can pass for the wrong reason or fail before exercising the real behavior.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
it('passes an isolated binding to the template', function () {
var scope = $rootScope.$new();
scope.user = { name: 'Mina' };
var element = $compile(
'<user-card person="user"></user-card>'
)(scope);
scope.$digest();
expect(element.find('.name').text()).toBe('Mina');
});Keep the fixture small but realistic. Include required attributes, transcluded content, or parent elements only when they are part of the directive’s contract.
Drive state changes and assert observable behavior
After linking, trigger the state change or DOM event the directive is designed to handle. AngularJS directives commonly observe model changes with $watch and register DOM listeners for interaction, so tests should exercise those paths rather than merely checking that compilation did not throw.
Test watched model changes
it('updates when the bound value changes', function () {
var scope = $rootScope.$new();
scope.label = 'Draft';
var element = $compile('<label-chip text="label"></label-chip>')(scope);
scope.$digest();
expect(element.text()).toContain('Draft');
scope.label = 'Published';
scope.$digest();
expect(element.text()).toContain('Published');
});Run a digest after changing scope data so AngularJS processes its watchers. Assert the resulting DOM or callback, not the existence of a watcher itself.
Test event listeners
it('invokes the supplied action on click', function () {
var scope = $rootScope.$new();
scope.save = jasmine.createSpy('save');
var element = $compile(
'<save-button on-save="save()"></save-button>'
)(scope);
scope.$digest();
element.triggerHandler('click');
expect(scope.save).toHaveBeenCalled();
});Use the event API appropriate to the test environment and the event registration used by the directive. If the directive depends on a particular event payload, provide that payload and assert the resulting contract.
Control HTTP requests with $httpBackend
When a directive causes an AngularJS $http request, do not let the test depend on a live server. Inject $httpBackend, declare the expected request and response, invoke the behavior, and call flush() to process the pending request.
Rank #4
- Used Book in Good Condition
it('renders data returned by the API', inject(function ($httpBackend) {
var scope = $rootScope.$new();
var element = $compile('<remote-status></remote-status>')(scope);
$httpBackend.expectGET('/api/status').respond(200, {
state: 'Ready'
});
scope.$digest();
$httpBackend.flush();
scope.$digest();
expect(element.text()).toContain('Ready');
}));Set the expectation before the action that starts the request. A missing expectation, an incorrect method or URL, or a forgotten flush() should fail the test instead of silently allowing a network call. Add separate tests for rejected responses only when the directive defines visible error behavior.
Choose assertions by behavior
| Behavior under test | Arrange | Drive | Assert |
|---|---|---|---|
| Rendering or binding | Scope values and required attributes | Compile, link, then digest | Text, structure, classes, or attributes |
| Watched state | Initial model value | Change the value and digest | Updated observable output |
| DOM interaction | Spy or callback on the scope | Trigger the registered event | Callback arguments or resulting DOM |
| HTTP interaction | $httpBackend expectation and response |
Invoke behavior, then flush | Success or error rendering promised by the directive |
This separation makes failures diagnostic: a rendering failure points to compilation, scope, or template setup; an interaction failure points to event wiring or callback handling; an HTTP failure points to the request expectation, response handling, or flush sequence.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep DOM responsibilities in directives
AngularJS concepts guidance places DOM-specific application behavior in directives. Code that accesses the DOM directly is difficult to test when it is scattered through controllers or services. Encapsulating that behavior in a directive gives the test a clear boundary: compile a small element, perform the relevant action, and inspect the resulting DOM.
Free tools Windows power users keep installed
One-click scans. No signup required.
Common failures and fixes
The directive never appears
- Confirm the directive’s module is loaded with
module('...'). - Check that the test uses the directive’s actual element, attribute, class, or comment form.
- Verify that the application and
angular-mocks.jsversions match the AngularJS version used by the project.
Bindings are empty or stale
- Create the expected parent or child scope before compilation.
- Provide every required attribute for an isolated binding.
- Run
scope.$digest()after initial linking and after changing model data.
An HTTP test hangs or fails unexpectedly
- Declare
expectGET,expectPOST, or the appropriate request expectation before triggering the request. - Match the exact URL and method generated by the directive.
- Call
$httpBackend.flush()only after the request has been initiated, then digest if the response updates scope.
The test passes but does not prove the feature
Replace assertions about private fields, directive definition objects, or merely successful compilation with an assertion about the rendered output, callback, event effect, or error state that a user can observe.
Account for AngularJS’s maintenance status
AngularJS support officially ended in January 2022. The official API reference identifies a 1.8.4 snapshot, while individual applications may use different builds, patches, browsers, and test runners. Treat these techniques as maintenance guidance for an existing AngularJS codebase, and verify the local dependency versions before adopting example syntax unchanged.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
