How rahimilahi/tfl works
This repository is a SpecFlow/Selenium acceptance-test suite for TfL’s journey planner. Feature scenarios describe user journeys; SpecFlow binds their steps to page-specific step definitions, which drive TfL pages through Selenium page objects and assert displayed results or validation messages. Scenario hooks create and quit Chrome, sharing its WebDriver through DriverHelper. The README also identifies reusable feature parameters. The feature source and some runtime wiring were not excerpted, so those links are shown only where documented or left out when unverified.
Main entry points: HomePageSteps.cs Home steps · JourneyPlanner.feature Journey scenarios · ResultsPageSteps.cs Results steps · DriverHelper.cs Driver helper
Components 10
Journey scenarios
- Journey scenarios
Features/JourneyPlanner.feature
Browser automation
- Home steps
StepDefinitions/HomePageSteps.cs - Results steps
StepDefinitions/ResultsPageSteps.cs - Home page object
Pages/HomePage.cs - Results page object
Pages/ResultsPage.cs - Driver helper
DriverHelper.cs - Scenario hooks
Hooks/Hooks1.cs
TfL website
- Chrome browser
- TfL journey planner
Other components
- Test runner
Connections 12
- Test runner → Journey scenarios: runs scenarios
- Journey scenarios → Home steps: dispatches steps
- Journey scenarios → Results steps: dispatches steps
- Scenario hooks → Driver helper: sets driver
Hooks/Hooks1.cs - Scenario hooks → Chrome browser: creates and quits
Hooks/Hooks1.cs - Home steps → Driver helper: uses driver
StepDefinitions/HomePageSteps.cs - Home steps → Home page object: calls page methods
StepDefinitions/HomePageSteps.cs - Results steps → Driver helper: uses driver
StepDefinitions/ResultsPageSteps.cs - Results steps → Results page object: calls page methods
StepDefinitions/ResultsPageSteps.cs - Home page object → TfL journey planner: locates and acts
- Results page object → TfL journey planner: locates and reads
- Home steps → TfL journey planner: navigates to
StepDefinitions/HomePageSteps.cs