tree: 4b68d724f02d8609f87d524b444c3b49309f67b0 [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. inference_update_1/
  18. inference_update_2/
  19. instantiate_to_bound/
  20. late_lowering/
  21. late_lowering_sentinel/
  22. macros/
  23. named_arguments_anywhere/
  24. new_const_insertion/
  25. nnbd/
  26. nnbd_mixed/
  27. no_such_method_forwarders/
  28. none/
  29. nonfunction_type_aliases/
  30. patterns/
  31. rasta/
  32. records/
  33. regress/
  34. runtime_checks/
  35. runtime_checks_new/
  36. sealed_class/
  37. set_literals/
  38. static_field_lowering/
  39. super_parameters/
  40. triple_shift/
  41. unified_collections/
  42. unscheduled_experiments/
  43. value_class/
  44. variance/
  45. views/
  46. expression.status
  47. incremental.status
  48. incremental_bulk_compiler_full.status
  49. incremental_bulk_compiler_smoke.status
  50. incremental_dartino.status
  51. modular.status
  52. outline.status
  53. README.md
  54. sdk.status
  55. strong.status
  56. textual_outline.status
  57. 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.