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