Same reason why you would split large modules in your regular code base: maintainability & navigability.

Over time as your definitions grow you will have steps that are closely related to certain parts or functionalities of your system, but not related to other steps in the definitions. Once the becomes large enough it will become harder to maintain and find the steps you are looking for. That’s a great indicator that you should starting up in multiple step files. For small projects, you may never reach this size.



Source link https://sqa.stackexchange.com/questions/28687/what-is-the--of-splitting-a--step-definition-file

LEAVE A REPLY

Please enter your comment!
Please enter your name here