tree: acd70c327d73b88d277bc50176409397883a96ed [path history] [tgz]
  1. dependency_resolution_order/
  2. disable_import_statements_validation/
  3. dont_rename_target/
  4. file_name_matches_import_statement/
  5. first_party_dependencies/
  6. first_party_file_and_directory_modules/
  7. generated_test_entrypoint/
  8. ignored_invalid_imported_module/
  9. invalid_imported_module/
  10. monorepo/
  11. naming_convention/
  12. naming_convention_binary_fail/
  13. naming_convention_library_fail/
  14. naming_convention_test_fail/
  15. python_ignore_dependencies_directive/
  16. python_ignore_files_directive/
  17. python_target_with_test_in_name/
  18. relative_imports/
  19. simple_binary/
  20. simple_binary_with_library/
  21. simple_library/
  22. simple_library_without_init/
  23. simple_test/
  24. subdir_sources/
  25. with_nested_import_statements/
  26. with_std_requirements/
  27. with_third_party_requirements/
  28. README.md
gazelle/testdata/README.md

Gazelle Python extension test cases

Each directory is a test case that contains BUILD.in and BUILD.out files for assertion. BUILD.in is used as how the build file looks before running Gazelle, and BUILD.out how the build file should look like after running Gazelle.

Each test case is a Bazel workspace and Gazelle will run with its working directory set to the root of this workspace, though, the test runner will find test.yaml files and use them to determine the directory Gazelle should use for each inner Python project. The test.yaml file is a manifest for the test - check for the existing ones for examples.