test: ✅ use TestBed instead of Testing Library in browser tests

to make it clear that browser mode and testing library are decoupled

Author: yjaaidi

apps/302-recipe-search-integration-browser-mode-solution/src/app/recipe/recipe-search.browser.spec.ts

@@ -1,4 +1,4 @@
-import { render } from '@testing-library/angular';
+import { TestBed } from '@angular/core/testing';
 import { page } from 'vitest/browser';
 import { recipeMother } from '../testing/recipe.mother';
 import {
@@ -17,18 +17,17 @@ describe(RecipeSearch.name, () => {
   });
 
   async function mountRecipeSearch() {
-    await render(RecipeSearch, {
+    TestBed.configureTestingModule({
       providers: [provideRecipeRepositoryFake()],
-      configureTestBed(testBed) {
-        testBed
-          .inject(RecipeRepositoryFake)
-          .setRecipes([
-            recipeMother.withBasicInfo('Burger').build(),
-            recipeMother.withBasicInfo('Salad').build(),
-          ]);
-      },
     });
 
+    TestBed.inject(RecipeRepositoryFake).setRecipes([
+      recipeMother.withBasicInfo('Burger').build(),
+      recipeMother.withBasicInfo('Salad').build(),
+    ]);
+
+    TestBed.createComponent(RecipeSearch);
+
     return {
       getRecipeNameEls() {
         return page.getByRole('heading');