tree: d1afa193bdf6374cf1ae04aa02775823b8447da3 [path history] [tgz]
  1. end2end/
  2. render/
  3. src/
  4. templates/
  5. comment_processable_test.dart
  6. dartdoc_options_test.dart
  7. grind_test.dart
  8. io_utils_test.dart
  9. markdown_processor_test.dart
  10. model_utils_test.dart
  11. package_meta_test.dart
  12. quiver_test.dart
  13. README.md
  14. resource_loader_test.dart
  15. source_linker_test.dart
  16. template_test.dart
  17. tool_runner_test.dart
  18. utils_test.dart
  19. warnings_test.dart
test/README.md

Tests

Most of dartdoc's tests are large end-to-end tests which read real files in real packages, in the testing/ directory. Unit tests exist in test/unit/.

Many of the end-to-end test cases should be rewritten as unit tests.

At some point, the distinction should flip, such that unit tests are generally located in test/, and end-to-end tests are found in a specific directory, or in files whose names signify the distinction.