Package net.thucydides.core.model

The Thucydides domain model, which represents acceptance test runs.

See:
Description

Class Summary

DataTable	A table of test data
DataTable.DataTableBuilder
DataTableRow
ErrorMessageFormatter	Converts a full WebDriver message into a shorter, more web-friendly format.
FailureAnalysis	Determine whether a given type of exception should result in a failure or an error.
NumericalFormatter
OutcomeCounter
Release	A release or version of a software project.
ReportNamer	Determies the correct default name for test reports.
Screenshot	Represents a screenshot stored during a test execution.
ScreenshotPermission
Stories	Helper methods to deal with stories and related classes.
Story	Represents a given user story.
TestDuration
TestOutcome	Represents the results of a test (or "scenario") execution.
TestOutcome.StepCountBuilder
TestResultList	A list of test results, used to determine the overall test result.
TestStep	An acceptance test run is made up of test steps.
TestStep.TestStepBuilder
TestTag
TestTag.TestTagBuilder

Enum Summary

ReportType	The report namer knows how to find names for these types of reports
TakeScreenshots
TestResult	Acceptance test results.
TestType

Package net.thucydides.core.model Description

The Thucydides domain model, which represents acceptance test runs. Thucydides is designed to make it easier to implement automated tests for web applications. In Thucydides, we implement tests to validate acceptance criteria. Each user story (use case/story card/...) should have a set of acceptance criteria that determine when the story is implemented. These acceptance criteria are automated by Webdriver-based tests, either using JUnit or easyb. In JUnit, a test case typically maps to a story card, though this is not a strict requirement. Using easyb, a test case maps to a story. Each acceptance criteria is automated by a unit test (JUnit) or a scenario (easyb). A given test is made up of test steps, which are executed in order, and can be organized and nested in test groups.