<itemvalue="Warning: At least one test in this suite creates an HttpClient. When running a test suite that uses TestWidgetsFlutterBinding, all HTTP requests will return status code 400, and no network request will actually be made. Any test expecting a real network connection and status code will fail. To test code that needs an HttpClient, provide your own HttpClient implementation to the code under test, so that your test can consistently provide a testable response to the code under test."/>
<itemvalue="create Main User Record"/>
<itemvalue="A mixin class for providing string and [DiagnosticsNode] debug representations describing the properties of an object. The string debug representation is generated from the intermediate [DiagnosticsNode] representation. The [DiagnosticsNode] representation is also used by debugging tools displaying interactive trees of objects and properties. See also: [debugFillProperties], which lists best practices for specifying the properties of a [DiagnosticsNode]. The most common use case is to override [debugFillProperties] defining custom properties for a subclass of [DiagnosticableTreeMixin] using the existing [DiagnosticsProperty] subclasses. [DiagnosticableTree], which extends this class to also describe the children of a tree structured object. [DiagnosticableTree.debugDescribeChildren], which lists best practices for describing the children of a [DiagnosticsNode]. Typically the base class already describes the children of a node properly or a node has no children. [DiagnosticsProperty], which should be used to create leaf diagnostic nodes without properties or children. There are many [DiagnosticsProperty] subclasses to handle common use cases."/>
<itemvalue="Finds [Semantics] widgets matching the given `label`, either by [RegExp.hasMatch] or string equality. The framework may combine semantics labels in certain scenarios, such as when multiple [Text] widgets are in a [MaterialButton] widget. In such a case, it may be preferable to match by regular expression. Consumers of this API __must not__ introduce unsuitable content into the semantics tree for the purposes of testing; in particular, you should prefer matching by regular expression rather than by string if the framework has combined your semantics, and not try to force the framework to break up the semantics nodes. Breaking up the nodes would have an undesirable effect on screen readers and other accessibility services. Sample code ```dart expect(find.bySemanticsLabel('Back'), findsOneWidget); ``` If the `skipOffstage` argument is true (the default), then this skips nodes that are [Offstage] or that are from inactive [Route]s."/>
debuggerx
3 years ago