Per the documentation (emphasis mine): You can create a spy object with several properties on it quickly by passing an array or hash of properties as a third argument to createSpyObj. In this case you won’t have a reference to the created spies, so if you need to change their spy strategies later, you will … Read more
Since Jasmine 2.6, this has been possible with spyOnProperty. To spy on the accessors for the foo property, do: spyOnProperty(o, ‘foo’) This allows you to replace the set and/or get accessor functions for an accessor property with a spy function. You can specify or set or get only as a third argument: spyOnProperty(o, ‘foo’, ‘get’) … Read more
See angular element api docs. If you use element.scope() you get the element’s scope that you defined in the scope property of your directive. If you use element.isolateScope() you get the entire isolated scope. For example, if your directive looks something like this : scope : { myScopeThingy : ‘=’ }, controller : function($scope){ $scope.myIsolatedThingy … Read more
In the following I list a set of potential causes and possibilities to fix/resolve them. How does AngularJS and Angular(2) Work / What can I check in the Browser Dev Mode I can’t explain it as well as Andrey Agibalov in his Blog here, so check it out (also for developers). Basically, the objects required … Read more
The best way to do this is to create a helper function somewhere and then mock that: var mynamespace = mynamespace || {}; mynamespace.util = (function() { function getWindowLocationHRef() { return window.location.href; } return { getWindowLocationHRef: getWindowLocationHRef } })(); Now instead of using window.location.href directly in your code simply use this instead. Then you can … Read more
1. Regarding with route check In case after first spec, user got logged in and the route changed. Make sure all are navigated before any test executed. expect(browser.getCurrentUrl()).toContain(‘#/the_route_of_logged_in’); // ‘#/’ is just illustration. You can remove it to make it shorter // => like this …toContain(‘the_route_of_logged_in’); 2. Regarding with click on tutorial browser.wait(EC.elementToBeClickable(tutorial), 10000); Do … Read more
You’re right that you can’t just set the input, you also need to dispatch the ‘input’ event. Here is a function I wrote earlier this evening to input text: function sendInput(text: string) { inputElement.value = text; inputElement.dispatchEvent(new Event(‘input’)); fixture.detectChanges(); return fixture.whenStable(); } Here fixture is the ComponentFixture and inputElement is the relevant HTTPInputElement from the … Read more
Depending on what you want to do, you can try: browser.waitForAngular(); or btnLoginEl.click().then(function() { // do some stuff }); to solve the promise. It would be better if you can do that in the beforeEach. NB: I noticed that the expect() waits for the promise inside (i.e. getCurrentUrl) to be solved before comparing.
In February 2017, they merged a PR adding this feature, they released in April 2017. so to spy on getters/setters you use: const spy = spyOnProperty(myObj, ‘myGetterName’, ‘get’); where myObj is your instance, ‘myGetterName’ is the name of that one defined in your class as get myGetterName() {} and the third param is the type … Read more
For primitive types (e.g. numbers, booleans, strings, etc.), there is no difference between toBe and toEqual; either one will work for 5, true, or “the cake is a lie”. To understand the difference between toBe and toEqual, let’s imagine three objects. var a = { bar: ‘baz’ }, b = { foo: a }, c … Read more