testbed

问题 I have referred the following link to get the answers, but I couldn't find any working solution for my scenario. Error: (SystemJS) Can't resolve all parameters for ActivatedRoute: (?, ?, ?, ?, ?, ?, ?, ?) Therefore, I have been trying to remove the Activated Route from the providers and still the test bed is not passing. It shows Error: No provider for ActivatedRoute! So here is my code, I want to run my test bed in the angular application which is using Jasmine. import { ActivatedRoute }

问题 I have referred the following link to get the answers, but I couldn't find any working solution for my scenario. Error: (SystemJS) Can't resolve all parameters for ActivatedRoute: (?, ?, ?, ?, ?, ?, ?, ?) Therefore, I have been trying to remove the Activated Route from the providers and still the test bed is not passing. It shows Error: No provider for ActivatedRoute! So here is my code, I want to run my test bed in the angular application which is using Jasmine. import { ActivatedRoute }

问题 When using the following configuration for a test fixture, I get complaints that the tag cannot be found. Substituting the MockSelectionToolComponent directly in AppModule works fine, so must be something else... // Add the imported module to the imports array in beforeEach beforeEach(() => { TestBed.configureTestingModule({ declarations: [MockSelectionToolComponent], imports: [ AppModule ] }).overrideModule(AppModule, { remove: { declarations: [SelectionToolComponent] } }).compileComponents(

问题 I am trying to test Google App Engine's new full text search functionality in Python with the development appserver. Is there a stub for the search that allows one to test it with the testbed local unit testing? The following is example code that throws an exception: #!/usr/bin/python from google.appengine.ext import testbed from google.appengine.api import search def foo(): d = search.Document(doc_id='X', fields=[search.TextField(name='abc', value='123')]) s = search.Index(name='one').add(d)

问题 I am using angular 5.2.0. I have a child component import { Component } from '@angular/core'; @Component({ template: `<div><\div>` }) export class ChildComponent { public childMethod() { ... } } and a parent component which accesses the child via ViewChild import { Component, ViewChild } from '@angular/core'; import { ChildComponent } from 'child.component'; @Component({ template: `<child-component #child><\child-component>` }) export class ParentComponent { @ViewChild('child') public child:

问题 I am using angular 5.2.0. I have a child component import { Component } from '@angular/core'; @Component({ template: `<div><\div>` }) export class ChildComponent { public childMethod() { ... } } and a parent component which accesses the child via ViewChild import { Component, ViewChild } from '@angular/core'; import { ChildComponent } from 'child.component'; @Component({ template: `<child-component #child><\child-component>` }) export class ParentComponent { @ViewChild('child') public child:

问题 In one of my unit test files, I have to mock several times the same service with different mocks. import { MyService } from '../services/myservice.service'; import { MockMyService1 } from '../mocks/mockmyservice1'; import { MockMyService2 } from '../mocks/mockmyservice2'; describe('MyComponent', () => { beforeEach(async(() => { TestBed.configureTestingModule({ declarations: [ MyComponent ], providers: [ { provide: MyService, useClass: MockMyService1 } ] }) .compileComponents(); }));

问题 I am new to Angular 2 testing. I am trying to figure out what is the difference in using testsbed.get() and just using inject at the test level. eg: beforeEach(() => { TestBed.configureTestingModule({ providers: [SomeService] }); const testbed = getTestBed(); someService= testbed.get(SomeService); }); }); vs it('test service', inject([SomeService], (someService: SomeService) => { 回答1: inject helper function was historically used since AngularJS as an alternative to direct injector calls. In

问题 I have some unit tests using Angular TestBed. Even if the tests are very simple, they run extremely slow (on avarage 1 test assetion per second). Even after re-reading Angular documentation, I could not find the reason of such a bad perfomance. Isolated tests, not using TestBed, run in a fraction of second. UnitTest import { Component } from "@angular/core"; import { ComponentFixture, TestBed, async } from "@angular/core/testing"; import { By } from "@angular/platform-browser"; import {

问题 I am trying to write a unit test for one of the components named Login.Component.ts whose code is given below. I tried various approaches but unable to get a successful response. Before explaining the component and service code, I want to know – TestBed – My understanding was that testbed in angular initiates and setup all the boilerplate code (required for testing like creating view, initializing and injecting service, creating routers and all this only for testing environment) by itself and