Significance of Maven,Svn,Jenkins in selenium webdriver?
Most Important in Selenium webdriver this topics and uses
The tools you name are used during different steps in the SDLC, they can be replaced by other
alternative tools
Example (partial) development life cycle:
Programming -> Check-in to version control -> Schedule build and run build -> Run automated test --->against build -> Report failing tests/buildsCheck-in to version control
After developers are finished with development they Check-In the code into a version controlsystem,
this to keep a history of all the changes. SVNs relation to Selenium testing is that you want to test against the latest version of the application. Also its advisable to keep the test-code close to the
application code and I would version it in the same repository.
Schedule build and run build
The build-server / continuous integration server monitors the version control, checks out any changes
and schedules a build against this version. Relation to Selenium testing is that Jenkins can prepare
the application and set it up in such a state that you can run the tests against it. Its possible to
use Maven as a tool to automate the building,integrating and or setup of the application instead of
using shell scripts.
Run automated test against build
After the build is OK, the build-server checks out and starts the Selenium tests. Maven can be used to
build and start tool that is fired by Jenkins to trigger the test start
Report failing tests/builds
The build-server reports any failing tests in its main overview or sends out e-mail to the person who
broke or monitors the build.
Alternative tools:
Build-tools
Build-servers
Version control systems
Most Important in Selenium webdriver this topics and uses
The tools you name are used during different steps in the SDLC, they can be replaced by other
alternative tools
Example (partial) development life cycle:
Programming -> Check-in to version control -> Schedule build and run build -> Run automated test --->against build -> Report failing tests/buildsCheck-in to version control
After developers are finished with development they Check-In the code into a version controlsystem,
this to keep a history of all the changes. SVNs relation to Selenium testing is that you want to test against the latest version of the application. Also its advisable to keep the test-code close to the
application code and I would version it in the same repository.
Schedule build and run build
The build-server / continuous integration server monitors the version control, checks out any changes
and schedules a build against this version. Relation to Selenium testing is that Jenkins can prepare
the application and set it up in such a state that you can run the tests against it. Its possible to
use Maven as a tool to automate the building,integrating and or setup of the application instead of
using shell scripts.
Run automated test against build
After the build is OK, the build-server checks out and starts the Selenium tests. Maven can be used to
build and start tool that is fired by Jenkins to trigger the test start
Report failing tests/builds
The build-server reports any failing tests in its main overview or sends out e-mail to the person who
broke or monitors the build.
Alternative tools:
Build-tools
Build-servers
Version control systems
