FlutterTestConfiguration class
Properties
-
build
↔ bool
-
If the application should be built prior to running the tests
Defaults to true
read / write
-
buildFlavor
↔ String
-
The build flavor to run the tests against (optional)
Defaults to empty
read / write
-
buildMode
↔ BuildMode
-
The default build mode used for running tests is --debug.
We are exposing the option to run the tests also in --profile mode
read / write
-
createWorld
↔ CreateWorld
-
An optional function to create a world object for each scenario.
read / write, inherited
-
customStepParameterDefinitions
↔ Iterable<CustomParameter>
-
Any user defined step parameters
read / write, inherited
-
dartDefineArgs
↔ List<String>
-
--dart-define args to pass into the build parameters. Include the name and value
for each. For example, --dart-define=MY_VAR="true" becomes ['MY_VAR="true"']
read / write
-
defaultTimeout
↔ Duration
-
The default step timeout - this can be override when definition a step definition
read / write, inherited
-
featureDefaultLanguage
↔ String
-
The default feature language
read / write, inherited
-
featureFileMatcher
↔ FeatureFileMatcher
-
read / write, inherited
-
featureFileReader
↔ FeatureFileReader
-
read / write, inherited
-
features
↔ Iterable<Pattern>
-
The path(s) to all the features.
All three Patterns are supported: RegExp, String,
Glob.
read / write, inherited
-
flutterBuildTimeout
↔ Duration
-
Duration to wait for Flutter to build and start the app on the target device
Slower machine may take longer to build and run a large app
Defaults to 90 seconds
read / write
-
flutterDriverMaxConnectionAttempts
↔ int
-
The maximum times the flutter driver can try and connect to the running app
Defaults to 3
read / write
-
flutterDriverReconnectionDelay
↔ Duration
-
Duration to wait before reconnecting the Flutter driver to the app.
On slower machines the app might not be in a state where the driver can successfully connect immediately
Defaults to 2 seconds
read / write
-
getAttachmentManager
↔ CreateAttachmentManager
-
used to get a new instance of an attachment manager class that is passed to the World context
read / write, inherited
-
hashCode
→ int
-
The hash code for this object. [...]
read-only, inherited
-
hooks
↔ Iterable<Hook>
-
Hooks that are run at certain points in the execution cycle
read / write, inherited
-
keepAppRunningAfterTests
↔ bool
-
Will keep the Flutter application running when done testing
Defaults to false
read / write
-
logFlutterProcessOutput
↔ bool
-
Logs Flutter process output to stdout
The Flutter process is use to start and driver the app under test.
The output may contain build and run information
Defaults to false
read / write
-
onAfterFlutterDriverConnect
↔ Future<void> Function(FlutterDriver driver)
-
Called after the successful connection of Flutter driver to the running application. Depending on your configuration this
method will be called on each new connection usually before each scenario is run.
read / write
-
onBeforeFlutterDriverConnect
↔ Future<void> Function()
-
Called before any attempt to connect Flutter driver to the running application, Depending on your configuration this
method will be called before each scenario is run.
read / write
-
order
↔ ExecutionOrder
-
The execution order of features - this default to random to avoid any inter-test dependencies
read / write, inherited
-
reporters
↔ Iterable<Reporter>
-
a list of reporters to use.
Built-in reporters: [...]
read / write, inherited
-
restartAppBetweenScenarios
↔ bool
-
restarts the application under test between each scenario.
Defaults to true to avoid the application being in an invalid state
before each test
read / write
-
runningAppProtocolEndpointUri
↔ String
-
An observatory url that the test runner can connect to instead of creating a new running instance of the target application
Url takes the form of
http://127.0.0.1:51540/EM72VtRsUV0=/ and usually printed to stdout in the form Connecting to service protocol: http://127.0.0.1:51540/EM72VtRsUV0=/
You will have to add the --verbose flag to the command to start your flutter app to see this output and ensure enableFlutterDriverExtension() is called by the running app
read / write
-
runtimeType
→ Type
-
A representation of the runtime type of the object.
read-only, inherited
-
stepDefinitions
↔ Iterable<StepDefinitionGeneric<World>>
-
The user defined step definitions that are matched with written steps in the features
read / write, inherited
-
stopAfterTestFailed
↔ bool
-
the program will stop after any test failed
read / write, inherited
-
tagExpression
↔ String
-
a filter to limit the features that are run based on tags
see https://docs.cucumber.io/cucumber/tag-expressions/ for expression syntax
read / write, inherited
-
targetAppPath
↔ String
-
The target app to run the tests against
Defaults to "lib/test_driver/app.dart"
read / write
-
targetAppWorkingDirectory
↔ String
-
Option to define the working directory for the process that runs the app under test (optional)
Handy if your app is separated from your tests as flutter needs to be able to find a pubspec file
read / write
-
targetDeviceId
↔ String
-
The target device id to run the tests against when multiple devices detected
Defaults to empty
read / write
-
verboseFlutterProcessLogs
↔ bool
-
Sets the --verbose flag on the flutter process
Defaults to false
read / write
