fix: update background processes to 2 instances

mdelapenya · mdelapenya · commit 96e42ea6dc16 · 2021-05-17T19:14:32.000+02:00
diff --git a/e2e/_suites/fleet/features/backend_processes.feature b/e2e/_suites/fleet/features/backend_processes.feature
@@ -6,8 +6,8 @@ Feature: Backend Processes
 Scenario Outline: Deploying the <os> agent
   Given a "<os>" agent is deployed to Fleet with "tar" installer
   When the "elastic-agent" process is in the "started" state on the host
-  Then there are "1" instances of the "filebeat" process in the "started" state
-    And there are "1" instances of the "metricbeat" process in the "started" state
+  Then there are "2" instances of the "filebeat" process in the "started" state
+    And there are "2" instances of the "metricbeat" process in the "started" state
 
 @centos
 Examples: Centos
@@ -23,8 +23,8 @@ Examples: Debian
 Scenario Outline: Deploying the <os> agent with enroll and then run on rpm and deb
   Given a "<os>" agent is deployed to Fleet
   When the "elastic-agent" process is in the "started" state on the host
-  Then there are "1" instances of the "filebeat" process in the "started" state
-    And there are "1" instances of the "metricbeat" process in the "started" state
+  Then there are "2" instances of the "filebeat" process in the "started" state
+    And there are "2" instances of the "metricbeat" process in the "started" state
 
 @centos
 Examples: Centos
@@ -57,8 +57,8 @@ Examples: Debian
 Scenario Outline: Restarting the installed <os> agent
   Given a "<os>" agent is deployed to Fleet with "tar" installer
   When the "elastic-agent" process is "restarted" on the host
-  Then there are "1" instances of the "filebeat" process in the "started" state
-    And there are "1" instances of the "metricbeat" process in the "started" state
+  Then there are "2" instances of the "filebeat" process in the "started" state
+    And there are "2" instances of the "metricbeat" process in the "started" state
 
 @centos
 Examples: Centos
@@ -75,8 +75,8 @@ Scenario Outline: Restarting the <os> host with persistent agent restarts backen
   Given a "<os>" agent is deployed to Fleet with "tar" installer
   When the host is restarted
   Then the "elastic-agent" process is in the "started" state on the host
-    And there are "1" instances of the "filebeat" process in the "started" state
-    And there are "1" instances of the "metricbeat" process in the "started" state
+    And there are "2" instances of the "filebeat" process in the "started" state
+    And there are "2" instances of the "metricbeat" process in the "started" state
 
 @centos
 Examples: Centos
