This library is not actual: it contains deprecated interfaces implementations and has no some actual concepts
Approach to integration tests
Basics:
- config-based test flow
- test flow consists of actions and has Composite structure
- any action in test flow - is Command & implementation of Action functional interface
- low coupling of Cucumber test cases with tests code: JUnit tests can be developed and run independent from Cucumber test cases
- POM (Page Object Model) approach to UI
Tools:
#Java #Selenium #JUnit #Cucumber #Spring
Basics of design:
#Composite #Command #Page Object
Tests:
package test.searchfilter.product.flight
Cucumber:
FlightSearchFilterCucumberIT class
JUnit:
OfferFilterFormSupplierFilterIT class
SearchFormSupplierFilterIT class
SearchFormDirectFlightFilterIT class
SearchFormFlightClassFilterIT class
SearchFormAirlineFilterIT class