Welcome to the testing world.
So previously, we helped create project structure of BDD framework.
Now I'm going to create a feature file in which we are going to use these keywords.
And in previous sessions we have already covered what is the meaning of each and every key word.
So I'm just going to explain one more time feature.
Key word is used for test suite scenario means test kits given when then and and keyword is going to
use to create the steps.
I'm just moving to the project.
I'm just hit on feature file.
If you want to use, you can install plugin for Girkin language.
So as of now, I'm not installing any plugin, but you can install if you want.
That's not mandatory.
So first of all, we need to use the feature that means test suite.
So I'm saying verifying.
Registration.
Functionality, no, and it's a feature keyword, then I'm going to use it's a capital effort, warrior
scenarios.
Naidoo means test case, so I'm writing like scenario registration with valid data now inside the scenario.
I'm going to write steps so given and we have already covered what's the meaning of each and every step.
So I'm just going directly and risk if user is on login page when the user is on registration page.
Shouldn't beach when user and dirs user name, if we have more than one steps, then we are going to
use end user and terse email I.D. and user and nurse password and user.
Click on Sign Up button.
As of now, I'm not writing all the steps what we need to write each and every step here.
Then if you want to make some verification, so I'm saying, then user should be registered.
Successfully so as of now, I have written a very simple test case, we call it scenario here in which
we have only a few steps.
As of now in this feature file, we have only one test case.
We can write any number of test cases.
I'm going to write one more test case.
I just copied that.
I'm going for second scenario with duplicate username.
So and I'm and duplicate name.
So I'm just creating two test cases here.
As of no one with the validate.
The other one is the duplicate user name data.
Everything seems to be OK.
I'm just doing it.
So here we have used a key word like feature, which is just to eat.
The best case scenario given means original patient when means when means steps, then for verification
and and is used for if you have more than one step or verification.
So in this session, we have created a feature file.
As of now, I have created only one feature file, which I have only two tasks.
We can create any number of feature five hidden the features folder in the feature folder, and each
piece of file can have any number of test cases.
So that's all we have for the session.
In next session, I'll show you how we can write code, which is going to execute against these lines.
And next session I'm going to write automation code.
That's all we have for the session.
Thanks watching this video.