 |
VOOZH | about |
|
VOOZH | about |
This page provides a high-level overview of how Ocaramba implements the Page Object Pattern. It describes the base class hierarchy that connects the core framework to specific test runner implementations and the reference page objects used for testing.
Ocaramba utilizes a structured inheritance model to separate framework logic, project-specific setup, and page-specific interactions. This structure ensures that test runners like NUnit, MsTest, and Xunit can consume the same page objects while maintaining their own lifecycle hooks.
The following diagram bridges the conceptual "Natural Language Space" of the Page Object Model to the "Code Entity Space" using specific classes and properties found in the codebase.
Diagram: POM Entity Mapping
Sources:
The bridge between the framework and a specific test suite is formed by two primary base classes.
ProjectTestBase: Inherits from the framework's TestBase Ocaramba.Tests.NUnit/ProjectTestBase.cs37 It manages the DriverContext Ocaramba.Tests.NUnit/ProjectTestBase.cs39 lifecycle, including starting the browser before tests (Start()) Ocaramba.Tests.NUnit/ProjectTestBase.cs81 and stopping it after (Stop()) Ocaramba.Tests.NUnit/ProjectTestBase.cs90 It typically contains the test runner attributes (like NUnit's [SetUp] and [TearDown]) and handles automatic screenshot capture on failure via SaveTestDetailsIfTestFailed Ocaramba.Tests.NUnit/ProjectTestBase.cs112ProjectPageBase: The base class for all Page Objects README.md107 It receives the DriverContext from the test and exposes the Driver property, allowing page objects to interact with the browser via Ocaramba's extensions.For details, see ProjectTestBase and ProjectPageBase.
Sources:
Ocaramba provides a dedicated project, Ocaramba.Tests.PageObjects, which serves as a reference implementation of the Page Object Model README.md60 This project contains page objects for "The Internet" (a popular test site) and various Kendo UI components.
These classes demonstrate the use of:
ElementLocator to define finding strategies (Id, Name, XPath, etc.) README.md113-114InternetPage README.md107-108 that provide methods to navigate to specific sub-pages.For details, see Page Objects: TheInternet and Kendo Examples.
Sources:
Ocaramba is runner-agnostic and provides implementation examples for the three major .NET testing frameworks.
Diagram: Test Runner Lifecycle Integration
| Project | Primary Purpose | Key Features |
|---|---|---|
Ocaramba.Tests.NUnit | Primary reference project | Performance tests Ocaramba.Tests.NUnit/ProjectTestBase.cs91-92 Data-Driven helpers Ocaramba.Tests.NUnit/ProjectBaseConfiguration.cs65-113 |
Ocaramba.Tests.MsTest | Microsoft Test support | CSV/XML Data-Driven Testing (DDT) [README.md:39-39]. |
Ocaramba.Tests.Xunit | Xunit support | Uses the TestFixture pattern for context [README.md:59-59]. |
For details, see Test Runner Integrations: NUnit, MsTest, Xunit.
Sources:
The Ocaramba.Tests.Features project integrates Behavior Driven Development (BDD) using SpecFlow README.md55 It uses BoDi for dependency injection to pass the DriverContext into step definition classes, allowing for clean Gherkin-based test scenarios.
For details, see BDD with SpecFlow (Ocaramba.Tests.Features).
Sources:
Ocaramba supports complex Data-Driven Testing (DDT) scenarios and flexible environment configuration.
ProjectBaseConfiguration: Consumes appsettings.json and environment-specific files (e.g., appsettings.{Env}.json) Ocaramba.Tests.NUnit/ProjectBaseConfiguration.cs51-54For details, see Test Runner Integrations: NUnit, MsTest, Xunit.
Sources: