tree: 040c0f1beb3232f3a1b0f359a45489a3117f6983 [path history] [tgz]
  1. render/
  2. src/
  3. templates/
  4. unit/
  5. dartdoc_integration_test.dart
  6. dartdoc_options_test.dart
  7. dartdoc_test.dart
  8. experiment_options_test.dart
  9. grind_test.dart
  10. html_generator_test.dart
  11. io_utils_test.dart
  12. markdown_processor_test.dart
  13. model_special_cases_test.dart
  14. model_test.dart
  15. model_utils_test.dart
  16. package_meta_test.dart
  17. README.md
  18. resource_loader_test.dart
  19. source_linker_test.dart
  20. template_test.dart
  21. tool_runner_test.dart
  22. utils_test.dart
  23. 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.