Trying to access the debugger using `browser.debugger()` isn't working
either, and by "isn't working" I mean to say that by going to runner.html
page, I can see "describe: app" followed by "should foobar" where the
error/stack trace follows:
Object function () {
var line = callerFile(3);
var scope = runner.$new();
// Make the dsl accessible on the current chain
scope.dsl = {};
angular.forEach(dslCache, function(fn, key) {
scope.dsl[key] = function() {
return dslCache[key].apply(scope, arguments);
};
});
// Make these methods work on the current chain
scope.addFuture = function() {
Array.prototype.push.call(arguments, line);
return angular.scenario.SpecRunner.
prototype.addFuture.apply(scope, arguments);
};
scope.addFutureAction = function() {
Array.prototype.push.call(arguments, line);
return angular.scenario.SpecRunner.
prototype.addFutureAction.apply(scope, arguments);
};
return scope.dsl[key].apply(scope, arguments);
} has no method 'debugger'
TypeError: Object function () {
var line = callerFile(3);
var scope = runner.$new();
// Make the dsl accessible on the current chain
On Sunday, December 22, 2013 1:41:32 AM UTC-6, [email protected] wrote:
>
> In my last email, I was trying to execute my scenarios from the command
> line. I'm able to actually have the tests from the browser. The problem I'm
> running into right now is that I can't seem to access the debugger method
> for the browser object.
>
>
> This is the scenario file
> 'use strict';
> describe('app', function() {
> it('should foobar', function() {
> console.log("browser: ", browser)
> window.bb = browser
> browser().debugger()
> });
> });
>
>
> // browser().debugger() results in `TypeError: Object #<Object> has no
> method 'debugger'`
>
> // This is what window.bb returns from the dev tools terminal:
> browser: function () { var line = callerFile(3); var scope =
> runner.$new(); // Make the dsl accessible on the current chain scope.dsl =
> {}; angular.forEach(dslCache, function(fn, key) { scope.dsl[key] =
> function() { return dslCache[key].apply(scope, arguments); }; }); // Make
> these methods work on the current chain scope.addFuture = function() {
> Array.prototype.push.call(arguments, line); return
> angular.scenario.SpecRunner. prototype.addFuture.apply(scope, arguments);
> }; scope.addFutureAction = function() {
> Array.prototype.push.call(arguments, line); return
> angular.scenario.SpecRunner. prototype.addFutureAction.apply(scope,
> arguments); }; return scope.dsl[key].apply(scope, arguments); }
>
> So, the browser object is available, and bb() will give me access to its
> available methods, but I don't see debugger as a method on the browser
> object. Is it still possible to access the debugger method from the browser
> object?
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/groups/opt_out.
