Test cases

[dgelessus]

The project currently has exactly zero automatic tests. This needs to change. In particular, the following features of the Python API should be tested:

• Reading resource files
  • Basic structure (types, IDs, data)
  • Empty resource files (i. e. basic resource file structure is there, but the type list contains no entries)
  • Ordering of resource types and IDs should match that in the file (no automatic sorting or reordering)
  • Additional resource file metadata (header system/application data, resource file attributes)
  • Additional resource metadata (names, resource attributes)
• Resource compression
  • Each of the supported compression algorithms
  • Compressed resource data header parsing
  • Integration with the main rsrcfork API
    • Automatic decompression (data vs. data_raw)
    • Exposing compressed resource metadata via compressed_info
• Different ways of opening resource files
  • Directly from a stream
    • Seekable and non-seekable streams
  • By path from data fork
  • On Mac only: By path from resource fork
  • On Mac only: By path with automatic data/resource fork selection
    • Graceful handling of nonexistant, empty or invalid resource forks

Testing the command-line interface is not a priority for now, for multiple reasons:

• It's not a proper API and not guaranteed to be stable
  • Some parts of the CLI are currently being reworked (or will be in the future)
• It's based on the Python API, so most issues that would affect the CLI will be detected by the Python API tests
• Testing terminal output is a pain and probably not worth the effort

[dgelessus]

Tests are now implemented.