-
Notifications
You must be signed in to change notification settings - Fork 49
/
README.md~
72 lines (37 loc) · 2.01 KB
/
README.md~
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
# selenium_BDD_framework
Behavioural driven development automation framework using selenium, cucumber-java, testng, maven, phantomjs
Tools and technologies used:
1. Language: Java 8
2. Testing framework: Testng
3. BDD framework: Cucumber jvm
4. Automation tool: Selenium webdriver
5. Build tool: maven
6. Logging: log4j
7. Headless browser: Phantomjs
Setting up the project:
$ cd selenium_BDD_framework
$ mvn clean install
Running the tests: There are 2 scenarios named as @scenario1 and @scenario2. Ran the tests on chrome54.0, firefox46 on ubuntu 14.04 64 bit
To run both scenarios (@scenario1 and @scenario2) (by default browser would be chrome):
$ mvn test
To run test with configurable browser (for firefox, use -Dbrowser=firefox)
$ mvn test -Dbrowser=chrome
To run tests headlessly
$ mvn test -Dheadless=yes
To run specific scenario:
$ mvn test -Dcucumber.options="--tags @scenario3"
To run multiple mentioned scenarios:
$ mvn test -Dcucumber.options="--tags @scenario3,@scenario2"
Features of the framework:
1. BDD framework using Cucumber-jvm. Features can be written easily using Given,When, Then etc.
2. Browser(chrome/firefox) can be configured at run time from command line.
3. Test can run in headless browser (Phantomjs), if required.
4. Screenshot would be taken if any scenario failed and saved under /outputFiles folder.
5. Html report gets generated after each test run and can be found /target/cucumber-html-report/index.html
Features package: It contains all different scenarios (tests) files
Framework: Contains framework level code which can be reused
Package: logger : It contains Log.java class which contains methods to show the logs on console and save the logs in LogFile.txt of each run.
Logic: contains all the classes where actions and assertions happens. Also, has class to start the execution.
OutputFiles: All the output files will be stored here (screenshots/csv/txt files)
Pages: It has web elements corresponding to the specific page.
Index.html will have execution report as follows: