Package net.thucydides.core.model

The Thucydides domain model, which represents acceptance test runs.

See: Description

Class Summary

Class	Description
BadgeBackground
CastMember
ContextIcon
DataSet	Created by john on 13/08/2014.
DataSetDescriptor	Created by john on 13/08/2014.
DataTable	A table of test data
DataTable.DataTableBuilder
DataTable.RowValueAccessor
DataTableRow
Downloadables
ErrorMessageFormatter	Converts a full WebDriver message into a shorter, more web-friendly format.
FeatureTagAsDefined	Created by john on 6/07/2016.
HeuristicTestResult
LastElement
NumericalFormatter
OutcomeCounter
PackageBasedLeafRequirements
Release	A release or version of a software project.
ReportData
ReportData.ReportDataBuilder
ReportNamer	Determies the correct default name for test reports.
ScenarioOutcomeCounter
Stories	Helper methods to deal with stories and related classes.
Story	Represents a given user story or feature.
TestDuration
TestOutcome	Represents the results of a test (or "scenario") execution.
TestOutcome.OptionalElements
TestOutcome.StepCountBuilder
TestOutcomeSummary	Lightweight copy of a TestOutcome.
TestResultComparison	A list of test results, used to determine the overall test result.
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
TitleBuilder

Enum Summary

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

Exception Summary

Exception	Description
TestFailureException	Created by john on 4/07/2014.

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.