tree: 9fdb58d607316827913d13e910c797f0878b3225 [path history] [tgz]
  1. agnostic/
  2. const_functions/
  3. constructor_tearoffs/
  4. dart2js/
  5. dartdevc/
  6. dartino/
  7. enhanced_enums/
  8. expression/
  9. extension_types/
  10. extensions/
  11. general/
  12. generic_metadata/
  13. implicit_getter_calls/
  14. incremental/
  15. inference/
  16. inference_new/
  17. instantiate_to_bound/
  18. late_lowering/
  19. late_lowering_sentinel/
  20. macros/
  21. named_arguments_anywhere/
  22. new_const_insertion/
  23. nnbd/
  24. nnbd_mixed/
  25. no_such_method_forwarders/
  26. none/
  27. nonfunction_type_aliases/
  28. rasta/
  29. regress/
  30. runtime_checks/
  31. runtime_checks_new/
  32. set_literals/
  33. static_field_lowering/
  34. super_parameters/
  35. triple_shift/
  36. unified_collections/
  37. unscheduled_experiments/
  38. value_class/
  39. variance/
  40. expression.status
  41. incremental.status
  42. incremental_bulk_compiler_full.status
  43. incremental_bulk_compiler_smoke.status
  44. incremental_dartino.status
  45. modular.status
  46. outline.status
  47. README.md
  48. sdk.status
  49. strong.status
  50. text_serialization.status
  51. textual_outline.status
  52. 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.

Dart 1.0 Compilation

./pkg/front_end/tool/fasta testing -DupdateExpectations=true compile/test1 compile/test2 ...

Dart 1.0 Outlines

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

Dart 2.0 (strong mode)

./pkg/front_end/tool/fasta 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.