If you are working on an AngularJS project, the choice is simple – Protractor: it is being made specifically for angular apps (though it can be used for non-angular apps also) supports angular-specific locator strategies (like by.model, by.repeater etc) waits for angular to start up during the page load (sync) it is being actively maintained … Read more
The assertion is there to confirm that a function would bring about program termination if it were executed in the current process (the details explains that the death test is invoked from a subprocess which allows the tests to continue despite the death). This is useful because some code may guarantee program termination / abortion … Read more
I’ll refer to parts of the first diagram from nvie.com’s Git Flow page throughout my answer; for completion, I’ve added a screenshot of it below. Today, the QA dept would like to take my new feature for a test drive. However, if I create them a build from my branch, none of the bug fixes … Read more
I just ran into this and solved it by switching to getting the service using the $injector explicitly: var EventingService, $rootScope; beforeEach(inject(function($injector) { EventingService = $injector.get(‘EventingService’); $rootScope = $injector.get(‘$rootScope’); })); I wish I could tell you why this works and why the simple beforeEach(inject(function(EventingService) { …. })); does not, but I don’t have the time … Read more
If you have access to an x86-based Mac then you can take advantage of the fact that Mac OS X has PowerPC emulation built in as well as developer tool support for both x86 (little endian) and PowerPC (big endian). This enables you to compile and run a big and little endian executable on the … Read more
It is all about promises (actually every protractor question is about promises). browser.wait() is not a blocking call, it schedules a command to wait for a condition: Schedules a command to wait for a condition to hold, as defined by some user supplied function. If any errors occur while evaluating the wait, they will be … Read more
That flag is telling gcc not to make a position independent executable (PIE). PIE is a precondition to enable address space layout randomization (ASLR). ASLR is a security feature where the kernel loads the binary and dependencies into a random location of virtual memory each time it’s run.