test(core): fix expectations that accidentally used incorrect matchers (#55294)

leonsenft · pkozlowski-opensource · commit afdcff3f7197 · 2024-04-12T07:38:55.000+02:00
Expect that the number of template executions is `===` to a number, rather than expect that it does not contain a number. As they were, these expectations would pass regardless of the expected value. PR Close #55294
diff --git a/packages/core/test/acceptance/change_detection_signals_in_zones_spec.ts b/packages/core/test/acceptance/change_detection_signals_in_zones_spec.ts
@@ -181,7 +181,7 @@ describe('CheckAlways components', () => {
     class App {
       val = val;
       ngOnInit() {
-        this.val.update(v => v+1);
+        this.val.update(v => v + 1);
       }
     }
     const fixture = TestBed.createComponent(App);
@@ -433,12 +433,12 @@ describe('OnPush components with signals', () => {
 
     fixture.detectChanges();
     expect(fixture.nativeElement.outerHTML).not.toContain('blue');
-    expect(fixture.componentInstance.numTemplateExecutions).not.toContain(1);
+    expect(fixture.componentInstance.numTemplateExecutions).toBe(1);
 
     useBlue.set(true);
     fixture.detectChanges();
     expect(fixture.nativeElement.outerHTML).toContain('blue');
-    expect(fixture.componentInstance.numTemplateExecutions).not.toContain(1);
+    expect(fixture.componentInstance.numTemplateExecutions).toBe(1);
   });
 
   it('can read a signal in a host binding', () => {
