From 07c2f316d17fed5f7de576753442b3070df3b840 Mon Sep 17 00:00:00 2001 From: Paul Gschwendtner Date: Thu, 22 Aug 2019 17:40:31 +0200 Subject: [PATCH] build: re-enable disabled gesture config test eaf70ca2a0600757041633976b29ab5a95d08296 temporarily disabled the gesture config tests because the blocklist didn't work. Now that the blocklist works on the framework side, we can re-enable this test again. Once this PR lands, we can update the SHA on the framework repo and add the gesture tests to the blocklist. --- src/material/core/gestures/gesture-config.spec.ts | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/src/material/core/gestures/gesture-config.spec.ts b/src/material/core/gestures/gesture-config.spec.ts index 79ae4412dc05..a9c70c9233af 100644 --- a/src/material/core/gestures/gesture-config.spec.ts +++ b/src/material/core/gestures/gesture-config.spec.ts @@ -3,13 +3,7 @@ import {Component} from '@angular/core'; import {HAMMER_GESTURE_CONFIG} from '@angular/platform-browser'; import {GestureConfig, MAT_HAMMER_OPTIONS} from './gesture-config'; -// TODO(kara): turn these tests back on when Material is using a release -// of Angular that contains the HammerModule. They need to be turned off -// for now in order to land https://github.com/angular/angular/pull/32203, -// which makes Hammer optional (so Material/FW integration tests don't start -// to fail). -/* tslint:disable */ -xdescribe('GestureConfig', () => { +describe('GestureConfig', () => { beforeEach(async(() => { TestBed.configureTestingModule({ declarations: [ButtonWithLongpressHander],