Google Git
Sign in
dart / sdk.git / refs/tags/2.18.0-155.0.dev / . / pkg / front_end / testcases
tree: f7e403b3703aba92b17fa970d07707f866304cf3 [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. instantiate_to_bound/
  19. late_lowering/
  20. late_lowering_sentinel/
  21. macros/
  22. named_arguments_anywhere/
  23. new_const_insertion/
  24. nnbd/
  25. nnbd_mixed/
  26. no_such_method_forwarders/
  27. none/
  28. nonfunction_type_aliases/
  29. rasta/
  30. regress/
  31. runtime_checks/
  32. runtime_checks_new/
  33. set_literals/
  34. static_field_lowering/
  35. super_parameters/
  36. triple_shift/
  37. unified_collections/
  38. unscheduled_experiments/
  39. value_class/
  40. variance/
  41. expression.status
  42. incremental.status
  43. incremental_bulk_compiler_full.status
  44. incremental_bulk_compiler_smoke.status
  45. incremental_dartino.status
  46. modular.status
  47. outline.status
  48. README.md
  49. sdk.status
  50. strong.status
  51. text_serialization.status
  52. textual_outline.status
  53. 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.