Skip to content

jpylyzer - create unittest to check whether all significant properties are mapped right way #14

@jstavel

Description

@jstavel
  • see appCtx-differ-cmdline.xml. It is main source.

    So there is bean metadataExtractors.
    See where it is used.

    There is jpylyzerMetadataExtractor in the file.
    It will be called in a unittest to get output.

  • please see, what structure the output is.

    There is ArraySet extractorProperties, identificationProperties, validationProperties, characterizationProperties in a file metadataSignificantProperties.
    All of them will be checked in the unittest.

  • Choose two images that jpylyzer can recognize. See property supportedFileExtensions in a file jpylyzerMetadataExtractor.

  • call jpylyzer by hand and try to recognize what values of significant properties the extractor gives.

  • save the values of significant properties for a given image into some structure. I think you can create spring application context for junit.

  • write junit test for bean jpylyzerMetadataExtractor to check, whether outputs it gives for a given image are the same as values by hand.

    If you have problem with collecting values of significant properties for given image I help you.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions