1
00:00:00,000 --> 00:00:01,000
Welcome to the testing world.

2
00:00:02,000 --> 00:00:07,000
So previously, we helped create project structure of BDD framework.

3
00:00:08,000 --> 00:00:13,000
Now I'm going to create a feature file in which we are going to use these keywords.

4
00:00:13,000 --> 00:00:18,000
And in previous sessions we have already covered what is the meaning of each and every key word.

5
00:00:18,000 --> 00:00:21,000
So I'm just going to explain one more time feature.

6
00:00:21,000 --> 00:00:30,000
Key word is used for test suite scenario means test kits given when then and and keyword is going to

7
00:00:30,000 --> 00:00:31,000
use to create the steps.

8
00:00:32,000 --> 00:00:34,000
I'm just moving to the project.

9
00:00:34,000 --> 00:00:38,000
I'm just hit on feature file.

10
00:00:38,000 --> 00:00:42,000
If you want to use, you can install plugin for Girkin language.

11
00:00:42,000 --> 00:00:46,000
So as of now, I'm not installing any plugin, but you can install if you want.

12
00:00:46,000 --> 00:00:47,000
That's not mandatory.

13
00:00:48,000 --> 00:00:52,000
So first of all, we need to use the feature that means test suite.

14
00:00:52,000 --> 00:00:54,000
So I'm saying verifying.

15
00:00:57,000 --> 00:00:58,000
Registration.

16
00:01:00,000 --> 00:01:10,000
Functionality, no, and it's a feature keyword, then I'm going to use it's a capital effort, warrior

17
00:01:11,000 --> 00:01:11,000
scenarios.

18
00:01:11,000 --> 00:01:25,000
Naidoo means test case, so I'm writing like scenario registration with valid data now inside the scenario.

19
00:01:25,000 --> 00:01:34,000
I'm going to write steps so given and we have already covered what's the meaning of each and every step.

20
00:01:34,000 --> 00:01:45,000
So I'm just going directly and risk if user is on login page when the user is on registration page.

21
00:01:48,000 --> 00:01:59,000
Shouldn't beach when user and dirs user name, if we have more than one steps, then we are going to

22
00:01:59,000 --> 00:02:16,000
use end user and terse email I.D. and user and nurse password and user.

23
00:02:17,000 --> 00:02:21,000
Click on Sign Up button.

24
00:02:21,000 --> 00:02:26,000
As of now, I'm not writing all the steps what we need to write each and every step here.

25
00:02:27,000 --> 00:02:35,000
Then if you want to make some verification, so I'm saying, then user should be registered.

26
00:02:38,000 --> 00:02:46,000
Successfully so as of now, I have written a very simple test case, we call it scenario here in which

27
00:02:46,000 --> 00:02:47,000
we have only a few steps.

28
00:02:48,000 --> 00:02:51,000
As of now in this feature file, we have only one test case.

29
00:02:51,000 --> 00:02:53,000
We can write any number of test cases.

30
00:02:55,000 --> 00:02:58,000
I'm going to write one more test case.

31
00:02:58,000 --> 00:02:59,000
I just copied that.

32
00:03:01,000 --> 00:03:11,000
I'm going for second scenario with duplicate username.

33
00:03:11,000 --> 00:03:16,000
So and I'm and duplicate name.

34
00:03:16,000 --> 00:03:20,000
So I'm just creating two test cases here.

35
00:03:21,000 --> 00:03:22,000
As of no one with the validate.

36
00:03:22,000 --> 00:03:24,000
The other one is the duplicate user name data.

37
00:03:25,000 --> 00:03:26,000
Everything seems to be OK.

38
00:03:28,000 --> 00:03:29,000
I'm just doing it.

39
00:03:30,000 --> 00:03:33,000
So here we have used a key word like feature, which is just to eat.

40
00:03:33,000 --> 00:03:42,000
The best case scenario given means original patient when means when means steps, then for verification

41
00:03:42,000 --> 00:03:49,000
and and is used for if you have more than one step or verification.

42
00:03:51,000 --> 00:03:53,000
So in this session, we have created a feature file.

43
00:03:53,000 --> 00:03:56,000
As of now, I have created only one feature file, which I have only two tasks.

44
00:03:57,000 --> 00:04:02,000
We can create any number of feature five hidden the features folder in the feature folder, and each

45
00:04:02,000 --> 00:04:04,000
piece of file can have any number of test cases.

46
00:04:06,000 --> 00:04:08,000
So that's all we have for the session.

47
00:04:08,000 --> 00:04:13,000
In next session, I'll show you how we can write code, which is going to execute against these lines.

48
00:04:15,000 --> 00:04:17,000
And next session I'm going to write automation code.

49
00:04:18,000 --> 00:04:19,000
That's all we have for the session.

50
00:04:20,000 --> 00:04:21,000
Thanks watching this video.