Sha256: f758a71d3b4df6e908d36cc0e40252ef08d3ba1442993ce24abd2cceaa256839
Contents?: true
Size: 1.37 KB
Versions: 2
Compression:
Stored size: 1.37 KB
Contents
Feature: structure json files In order to have programmatic ability to introspect resulting packages, we generate some extra files. Scenario: auto-generation of tree.json and scripts.json When I run "jsus -i Basic -o tmp" Then the following files should exist: | tmp/tree.json | | tmp/scripts.json | And file "tmp/tree.json" should contain valid JSON And file "tmp/tree.json" should contain JSON equivalent to """ { "Library": { "Color": { "desc": "A library to work with colors", "requires": [ ], "provides": [ "Color" ] } }, "Widget": { "Input": { "Input.Color": { "desc": "Cool colorpicker for everyone to enjoy", "requires": [ "Color" ], "provides": [ "Input.Color" ] } } } } """ And file "tmp/scripts.json" should contain valid JSON And file "tmp/scripts.json" should contain JSON equivalent to """ { "Package": { "desc": "Jsus package with correct order set", "provides": [ "Color", "Input.Color" ], "requires": [ ] } } """
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
jsus-0.2.2 | features/command-line/structure_json.feature |
jsus-0.2.1 | features/command-line/structure_json.feature |