tree: b025c4b19c6d84e7ef7c4dc22b12e481c8b91a40 [path history] [tgz]
  1. class_modifiers/
  2. const_functions/
  3. constructor_tearoffs/
  4. coverage/
  5. dart2js/
  6. dart2wasm/
  7. dartdevc/
  8. dartino/
  9. enhanced_enums/
  10. enhanced_parts/
  11. expression/
  12. extension_types/
  13. extensions/
  14. general/
  15. generic_metadata/
  16. getter_setter_error/
  17. implicit_getter_calls/
  18. incremental/
  19. inference/
  20. inference_new/
  21. inference_update_1/
  22. inference_update_2/
  23. inference_update_3/
  24. inference_update_4/
  25. inference_using_bounds/
  26. instantiate_to_bound/
  27. late_lowering/
  28. late_lowering_sentinel/
  29. macros/
  30. named_arguments_anywhere/
  31. nnbd/
  32. no_such_method_forwarders/
  33. none/
  34. nonfunction_type_aliases/
  35. null_aware_elements/
  36. offsets/
  37. patterns/
  38. rasta/
  39. records/
  40. regress/
  41. runtime_checks/
  42. runtime_checks_new/
  43. sealed_class/
  44. set_literals/
  45. static_field_lowering/
  46. super_parameters/
  47. triple_shift/
  48. unified_collections/
  49. unscheduled_experiments/
  50. variance/
  51. wildcard_variables/
  52. expression.status
  53. incremental.status
  54. incremental_bulk_compiler_full.status
  55. incremental_bulk_compiler_smoke.status
  56. incremental_dartino.status
  57. modular.status
  58. outline.status
  59. OWNERS
  60. README.md
  61. sdk.status
  62. strong.status
  63. textual_outline.status
  64. weak.status
pkg/front_end/testcases/README.md

Overview

The testcases in this directory and its subdirectory are all compiled in various different configurations designed to test various aspects of Fasta (or more generally, package:front_end).

The configurations are described below.

The source of truth for these configurations is the file pkg/front_end/testing.json.

Updating all expectations

To update test expectations for all tests at once, run:

dart pkg/front_end/tool/update_expectations.dart

Note that this takes a long time and should only be used when many tests need updating.

Updating expectations for a single test

To update the expectations for a specific test, provide the folder and test name as an argument.

For example, if you want to update the test expectations for a test, such as pkg/front_end/testcases/general/abstract_instantiation.dart, then run:

dart pkg/front_end/tool/update_expectations.dart general/abstract_instantiation

Updating expectations for all tests in a folder

If you want to update the test expectations for a specific folder of tests such as the pkg/front_end/testcases/general/ folder, then run:

dart pkg/front_end/tool/update_expectations.dart general/...

Dart 3.0 Outlines

./pkg/front_end/tool/cfe testing -DupdateExpectations=true outline/test1 outline/test2 ...

Dart 3.0 (strong mode)

./pkg/front_end/tool/cfe testing -DupdateExpectations=true -DupdateComments=true strong/test1 strong/test2 ...

Note: strong mode configuration additionally parses comments in the test file and can precisely match internal details of the compiler such as the inferred type of an expression or if a warning was emitted at a given location.