使用Jest运行测试时,Adal.service.ts在角度上对我不起作用

如何解决使用Jest运行测试时,Adal.service.ts在角度上对我不起作用

请帮助我。

我要迁移到Jest来运行ANGULAR的单元测试,但是执行时出现错误:

失败 src / app / modules / dashboard / components / navbar / navbar.component.spec.ts
测试套件无法运行

ReferenceError: AuthenticationContext is not defined

   6 | 
   7 | declare var AuthenticationContext: adal.AuthenticationContextStatic;
>  8 | const createAuthContextFn: adal.AuthenticationContextStatic = AuthenticationContext;
     |                                                               ^
   9 | 
  10 | @Injectable()
  11 | export class AdalService {

  at Object.<anonymous> (src/app/core/authentication/adal.service.ts:8:63)
  at Object.<anonymous> (src/app/core/authentication/adal-access.guard.ts:3:1)
  at Object.<anonymous> (src/app/modules/dashboard/components/navbar/navbar.component.spec.ts:5:1)

测试套件:1个失败,总共1个

当我用Jest运行测试时,Adal.service.ts在角度上对我不起作用。

当我与业力一起运作时,它会起作用

这是测试:

import { Store } from '@ngrx/store';
import { RouterTestingModule } from '@angular/router/testing';
import { MatMenuModule } from '@angular/material/menu';
import { AdalConfigService } from './../../../../core/authentication/adal-config.service';
import { AdalAccessGuard } from './../../../../core/authentication/adal-access.guard';
import { AdalService } from '@authentication/adal.service';
import { environment } from '@env/environment';
import { APP_CONFIG } from '@app/app.config';
import { async,ComponentFixture,TestBed } from '@angular/core/testing';

import { NavbarComponent } from './navbar.component';

describe('NavbarComponent',() => {
    let component: NavbarComponent;
    let fixture: ComponentFixture<NavbarComponent>;

    beforeEach(async(() => {
        TestBed.configureTestingModule({
            declarations: [NavbarComponent],imports: [
                RouterTestingModule,MatMenuModule
            ],providers: [
                {
                    provide: Store,useValue: {
                        dispatch: jest.fn(),pipe: jest.fn()
                    }
                },AdalService,AdalConfigService,AdalAccessGuard,{
                    provide: APP_CONFIG,useValue: {
                        apiEndpoint: environment.apiEndPoint,clientId: environment.azureActiveDirectory.clientId,tenantId: environment.azureActiveDirectory.tenantId,resource: environment.azureActiveDirectory.resource,redirectUri: environment.azureActiveDirectory.redirectUri
                    }
                }]
        })
            .compileComponents();
    }));

    beforeEach(() => {
        let mockAdalError;
        let mockAdal;
        fixture = TestBed.createComponent(NavbarComponent);
        component = fixture.componentInstance;
        mockAdalError = false;
        mockAdal = {
            userName: 'xxx',profile: {
                aud: 'xxx',}
        };
    });

    it('should create',() => {
        expect(component).toBeTruthy();
    });

});
  • 经过组件测试:
import { AdalService } from '@authentication/adal.service';
import { Component,OnInit } from '@angular/core';

@Component({
  selector: 'app-navbar',templateUrl: './navbar.component.html',styleUrls: ['./navbar.component.scss']
})
export class NavbarComponent implements OnInit {

  public name;
  public surname;
  public email;

  constructor( private adalService: AdalService ) { }

  ngOnInit() {
    this.loadUserInfo(this.adalService.userInfo);
  }

  onLogout(): void {
    this.adalService.logout();
  }

  loadUserInfo(adalUser: any): void {
    if (adalUser) {
      this.name = XXX;
      this.email = XXX;
    } else {
      this.name = 'No disponible';
      this.email = 'No disponible';
    }
  }

}

这是ADAL的服务

import { Injectable } from '@angular/core';
import { Observable,Subscriber } from 'rxjs';
import { retry } from 'rxjs/operators';
import { AdalConfigService } from './adal-config.service';
import { adal } from 'adal-angular';

declare var AuthenticationContext: adal.AuthenticationContextStatic;
const createAuthContextFn: adal.AuthenticationContextStatic = AuthenticationContext;

@Injectable()
export class AdalService {
    private context: adal.AuthenticationContext;
    constructor(private configService: AdalConfigService) {
        this.context = new createAuthContextFn(configService.adalSettings);
    }
    login() {
        this.context.login();
    }
    logout() {
        this.context.logOut();
    }
    get authContext() {
        return this.context;
    }
    handleWindowCallback() {
        this.context.handleWindowCallback();
    }
    public get userInfo() {

        return this.context.getCachedUser();
    }
    public get accessToken() {
        return this.context.getCachedToken(this.configService.adalSettings.clientId);
    }
    public get isAuthenticated() {
        return this.userInfo && this.accessToken;
    }

    public isCallback(hash: string) {
        return this.context.isCallback(hash);
    }

    public getLoginError() {
        return this.context.getLoginError();
    }

    public getAccessToken(endpoint: string,callbacks: (message: string,token: string) => any) {

        return this.context.acquireToken(endpoint,callbacks);
    }

    public acquireTokenResilient(resource: string): Observable<any> {
        return new Observable<any>((subscriber: Subscriber<any>) =>
            this.context.acquireToken(resource,(message: string,token: string) => {
                token ? subscriber.next(token) : subscriber.error(message);
            })
        ).pipe(retry(3));
    }
}

我正在使用以下版本:“ adal-angular”:“ ^ 1.0.17”,

解决方法

解决您的问题

要使安装顺利进行,必须在全局某处初始化AuthenticationContext。我认为这是通过在您的index.htmlpolyfills.ts中加载一些adal脚本在您的代码的浏览器中发生的。

Jest不会加载这些文件,因此不会在任何地方初始化AuthenticationContext。

使用变量declare var AuthenticationContext: adal.AuthenticationContextStatic的声明,您告诉TypeScript:“我保证我会在其他地方全局初始化此变量”,但看来您不是在Jest运行中这样做。

解决方案是在需要的测试文件中导入用于初始化AuthenticationContext的脚本,或者在需要的文件中手动进行脚本:

// 1. Initialize Variable
// not sure if you can initialize it like this,see the adal docs or source code
globalThis.AuthenticationContext = new AuthenticationContext();

// 2. Tell TypeScript compiler about this variable
declare const AuthenticationContext: adal.AuthenticationContextStatic;

单元测试

您谈论的是单元测试,但是您的测试看起来并不像单元测试,因为您没有以孤立的方式对其进行测试。

如果要按单元测试每个组件,则完全不应实例化AuthenticationContext来测试NavBar。并非来自NavBar内部的所有其他组件和对象都应被模拟并作为虚拟对象提供。这样也可以间接解决您的问题。

要更好地理解这一点,请查看《 Angular测试指南》和jest文档。

欢呼和快乐的编码!

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-