Skip to content

Architectural overview

Jump to bottom
nreijmersdal edited this page Feb 1, 2013 · 4 revisions

SenBot is implemented using:

  • Java
  • Maven
  • JUnit
  • Spring
  • Cucumber
  • Selenium

Architectural overview

#The SenBot SenBotContext(Singleton) = Instantiating of all objects
SeleniumManager = Setting up of selenium
EnvironmentManager = Definition of the test environment
CucumberManager = Cucumber implementation in Java
Services = High level modules for dedicated tasks
The objects of the core are managed via spring.

#The SenBot test layer AbstractBaseStepDefinition = Base class of all cucumber test
Generic step definitions = The glue between cucumbers gherkin language and Java
The test projects

Test projects are implementations of SenBot. Tests can be specified using gherkin or JUnit. Tests are run by JUnit started by an IDE like Eclipse or via command line using Maven.

They consist of:

Runner = One or more test runners
Implementation specific step definitions = The glue between cucumbers gherkin language and Java
Feature files = Test specification in cucumbers gherkin language

Clone this wiki locally