Thursday, March 13, 2025

bdd – Writing behavioural options/eventualities for utility with many proccesses and sections


I am attempting to start out automation on the internet utility that I am presently manually testing.
I used to be steered to do it utilizing BDD, so I began reseaching about it, and as I began writing my first options, I spotted that there’s simply an excessive amount of and I get overwhelmed.

My utility was has like 10 menu gadgets each being a enterprise unit, the one which I am testing has like 9 – 10 sub menu gadgets (screens) that resemble every a strategy of my enterprise unit, and resulting from code reutilization, most of the screens I am testing share parts with different enterprise items, so there have been some bugs resulting from adjustments “out of my backlog”, that is why I wish to check display screen information validations.
Additionally every display screen has at the least 3 – 7 sections (the sections proven rely on the info enter) and every component of every part has completely different validations. Lastly all of the proccesses begin with the identical one, however a few of then require greater than two or three proccesses beforehand executed.

Which ought to be my strategy?

a) Ought to I attempt to write the options focusing the validation of every part separatedly? And in some unspecified time in the future automate the complete completely satisfied path of the proccess?

b) Or possibly I ought to keep into the overall “movement” and write like i am attempting to do the entire proccess itself every time? Having tons of eventualities the place I finish the movement earlier due to the testing of the completely different validations?

Examples of what I assumed:
Suppose the primary strategy of all, the check creation proccess, there you possibly can create assessments, you may have for instance, sort STANDARD and kind SPECIAL assessments, sort SPECIAL shows an extra part.
Additionally for simplification SA => Part A. Parenthesis will likely be set of knowledge for present part and kind of check, so SA(STANDARD) would be the set of knowledge for part A for a Normal Check.

   Background:
          Given I'm in creation web page

a) Function: As A person I would like to have the ability to create my assessments
      State of affairs: Finishing SA with appropriate values
          After I full with appropriate SA(STANDARD) values
          Then validation goes okay
          And SC is proven

      State of affairs: Finishing SA with appropriate values
          After I full with appropriate SA(SPECIAL) values
          Then validation goes okay
          And SB is proven
          And SC is proven

      State of affairs: Finishing SA with incorrect values
          ... ... ... -> web page validations

      State of affairs: Partially finishing SA 
          ... ... ... -> different web page validations

      State of affairs: Finishing SC with appropriate values
          Given I accomplished SA with appropriate SA(STANDARD) values
          And SB and SC are proven
          After I full SC with appropriate SC(STANDARD) values
          ... ... ...
     #And in some unspecified time in the future I'll automate the "completely satisfied path", properly the completely satisfied path could possibly be initially although

b) Function: As A person I would like to have the ability to create my assessments
      State of affairs: Right Creation of a STANDARD check
          After I full SA with appropriate SA(STANDARD) values
          And I full SC with appropriate SC(STANDARD) values
          And I create the check
          Then the check is created efficiently

      State of affairs: Right Creation of a SPECIAL check
          After I full SA with appropriate SA(SPECIAL) values
          And I full SC with appropriate SC(SPECIAL) values
          And I full SB with appropriate SB(SPECIAL) values
          And I create the check
          Then the check is created efficiently

      State of affairs: Making an attempt the creation of a STANDARD check with incorrect SA(STANDARD) values
          Given I'm in creation web page
          After I full SA with incorrect SA(STANDARD) values
          And I create the check
          Then the check isn't created
          And the display screen exhibits validation errors on 

      State of affairs: Making an attempt the creation of a STANDARD check with incorrect SB(STANDARD) values
          Given I'm in creation web page
          And I accomplished SA with appropriate SA(STANDARD) values
          After I full SB with incorrect SB(STANDARD) values
          And I create the check
          Then the check isn't created
          And the display screen exhibits validation errors

Effectively, I do know I wrote an excessive amount of, I used to be attempting to indicate what I have been considering. Any assist or suggestion is way appreciated.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles

PHP Code Snippets Powered By : XYZScripts.com