Add Search tests

playwright.config.ts

@@ -45,14 +45,14 @@ export default defineConfig({
 
   /* Configure projects for major browsers */
   projects: [
-    {
-      name: "chromium",
-      use: {
-        ...devices["Desktop Chrome"],
-        ...DESKTOP_CONFIG,
-      },
-      dependencies: ["setup-ui-data"],
-    },
+    // {
+    //   name: "chromium",
+    //   use: {
+    //     ...devices["Desktop Chrome"],
+    //     ...DESKTOP_CONFIG,
+    //   },
+    //   dependencies: ["setup-ui-data"],
+    // },
 
     {
       name: "firefox",
@@ -63,14 +63,14 @@ export default defineConfig({
       dependencies: ["setup-ui-data"],
     },
 
-    {
-      name: "webkit",
-      use: {
-        ...devices["Desktop Safari"],
-        ...DESKTOP_CONFIG,
-      },
-      dependencies: ["setup-ui-data"],
-    },
+    // {
+    //   name: "webkit",
+    //   use: {
+    //     ...devices["Desktop Safari"],
+    //     ...DESKTOP_CONFIG,
+    //   },
+    //   dependencies: ["setup-ui-data"],
+    // },
 
     {
       name: "setup-ui-data",

tests/ui/features/@search/search.feature

@@ -0,0 +1,74 @@
+Feature: Search
+	As a Devsecops Engineer
+	I want to perform searching across vulnerabilities, SBOMs and packages, specific searches for CVE IDs, SBOM titles, package names and show results that are easy to navigate to the specific item of interest.
+
+Background:
+	Given User is authenticated
+	And User is on the Search page
+
+# Scenario: User visits search page without filling anything
+# 	When user starts typing a "" in the search bar
+# 	And user presses Enter
+# 	Then a total number of "SBOMs" should be visible in the tab
+# 	And a total number of "Packages" should be visible in the tab
+# 	And a total number of "CVEs" should be visible in the tab
+# 	And a total number of "Advisories" should be visible in the tab
+
+@only
+Scenario Outline: User toggles the <types> list and manipulates the list
+ 	When User selects the Tab "<types>" 
+	Then the "<types>" list should have specific filter set
+	And the "<types>" list should be sortable
+	And the "<types>" list should be limited to 10 items
+	And the user should be able to switch to next "<types>" items
+	And the user should be able to increase pagination for the "<types>"
+	And First column on the search results should have the link to "<types>" explorer pages
+
+	Examples:
+	|types|
+	# |SBOMs|
+	# |Packages|
+	|Vulnerabilities|
+	# |Advisories|
+
+Scenario Outline: Download Links on the <types> Search Result list
+	When User selects the Tab "<types>" 
+	Then Tab "<types>" is visible
+	And Download link should be available for the "<types>" list
+
+        Examples:
+	|types|
+	|SBOMs|
+	|Advisories|
+
+# Scenario Outline: Autofill shows results matched on <input> 
+# 	When user starts typing a "<input>" in the search bar  
+# 	Then the autofill dropdown should display items matching the "<input>" 
+# 	And the results should be limited to 5 suggestions
+
+# 	Examples:
+# 	|input|
+# 	|quarkus-bom|
+# 	|CVE-2022-45575|
+# 	|Certain NETGEAR devices|
+
+Scenario: Search bar should not preview anything when no matches are found 
+	And user starts typing a "non-existent name" in the search bar
+	Then The autofill drop down should not show any values
+
+Scenario Outline: User searches for a specific "<type>"
+ 	When user types a "<type-name>" in the search bar
+ 	And user presses Enter
+	And User selects the Tab "<types>" 
+ 	Then the "<types>" list should display the specific "<type-name>"
+	And the list should be limited to 10 items or less
+ 	And the user should be able to filter "<types>" 
+ 	And user clicks on the "<type-name>" "<type>" link
+ 	And the user should be navigated to the specific "<type-name>" page 
+
+	Examples:
+	|type|types|type-name|
+	|SBOM|SBOMs|quarkus-bom|
+	|CVE|Vulnerabilities|CVE-2022-45787|
+	|Package|Packages|quarkus|
+	|Advisory|Advisories|CVE-2022-45787|