diff --git a/tests/bdd/volgroup_vgpattern_bdd.feature b/tests/bdd/volgroup_vgpattern_bdd.feature
index 76ab5dc1..8be80a2c 100644
--- a/tests/bdd/volgroup_vgpattern_bdd.feature
+++ b/tests/bdd/volgroup_vgpattern_bdd.feature
@@ -33,16 +33,18 @@ Feature: Validate vgpattern and volgroup based scheduling.
           Then pvc should not be Bound
           And lvmvolume cr should not be created
 
-  
-      Scenario: test pvc with larger size then vg free space
-          Given both <vg> are created with their respective <size>
-          And sc is created with volgroup as "lvmvg"
-          When a pvc is created with size "1.3G"
-          Then pvc should not be bound
-          And lvmvolume cr should not be created
-          When "lvmvg" is extended to "1.5G"
-          Then pvc should be Bound
-          And lvmvolume cr should have expected vg value
+   Background:
+        Given Single lvmnode cluster is configured
+        And both <vg> are created with their respective <size>
+
+        Scenario: test pvc with larger size then vg free space
+            Given sc is created with volgroup parameter as "lvmvg"
+            When a pvc is created with size "1.3G"
+            Then pvc should not be bound
+            And lvmvolume cr should not be created
+            When "lvmvg" is extended to "1.5G"
+            Then pvc should be Bound
+            And lvmvolume cr should have expected vg value
 
             Examples:
                 |  vg        | size     |