Add tests (#53)

* Add tests

* Configure test matrix

* Update jsonschema

* Fix schema

* Set validation output to pretty

* Fix package install

* Update PR template

* Force LF line endings

Author: innovate-invent

.gitattributes

@@ -0,0 +1,9 @@
+* text=auto
+
+*.yaml text
+*.yml text
+*.json text
+*.txt text
+*.md text
+*.py text
+*.sh text

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md renamed to .github/pull_request_template.md

@@ -1,86 +1,88 @@
-<!--
-Thank you for your interest in contributing to the JMESPath Specification.
-
-Before creating a pull request, please ensure that the feature or change has been fully discussed in a discussion and the discussion has been assigned a JEP tag.
-
-This PR should include a JEP specification file based off TEMPLATE.md, named with the pattern "jep-###-title.md".
-Additionally, the PR should include any intended modifications to the GRAMMAR file.
-
-Please complete the required sections below:
--->
-
-# \<TITLE>
-
-|||
-|---|---
-| **JEP**    | 
-| **Author** | \<author>
-| **Created**| \<date>
-| **[SemVer](https://semver.org/spec/v2.0.0.html#summary)** | MAJOR\|MINOR\|PATCH
-| **[Discussion #](https://github.com/jmespath-community/jmespath.jep/discussions)** | [##](https://github.com/jmespath-community/jmespath.jep/discussions/##)
-
-*Please discuss the merit of the JEP in the linked discussion. PR discussion should be limited to proofing the content of the PR and the PR proposal inital comment*
-
-## Abstract
-
-\<copy from JEP>
-
-## Implementation Survey
-
-*Omit this section if not relevant*
-
-Provide a minimal demonstration of how the proposed functionality would be implemented for each programming language.
-Include links to any proposed dependencies. This is to ensure that each language can support the proposed functionality, allows for
-the review of any additional dependencies that would need to be included with each implementation, provides reference for implementers,
-and ensures that each proposed implementation in each language has consistent behaviour across all languages.
-
-
-### Javascript/Typescript
-
-```typescript
-```
-
-### NodeJS
-
-```nodejs
-```
-
-### Python
-
-```python3
-```
-
-### C/C++
-
-```c++
-```
-
-### C#
-
-```c#
-```
-
-### PHP
-
-```php
-```
-
-### Java
-
-```java
-```
-
-### Rust
-
-```rust
-```
-
-### Go
-
-```go
-```
-
-### Lua
-
-```lua
-```
+<!--
+Thank you for your interest in contributing to the JMESPath Specification.
+
+Before creating a pull request, please ensure that the feature or change has been fully discussed in a discussion and the discussion has been assigned a JEP tag.
+
+This PR should include a JEP specification file based off TEMPLATE.md, named with the pattern "jep-###-title.md", and a compliance test json in either
+grammar/ or functions/ as appropriate.
+Additionally, the PR should include any intended modifications to the GRAMMAR file.
+
+Please complete the required sections below:
+-->
+Please keep PR discussion strictly about the content of the PR and any comments on the merit of the proposal in the linked discussion.
+
+# \<TITLE>
+
+|||
+|---|---
+| **JEP**    | 
+| **Author** | \<author>
+| **Created**| \<date>
+| **[SemVer](https://semver.org/spec/v2.0.0.html#summary)** | MAJOR\|MINOR\|PATCH
+| **[Discussion #](https://github.com/jmespath-community/jmespath.jep/discussions)** | [##](https://github.com/jmespath-community/jmespath.jep/discussions/##)
+
+*Please discuss the merit of the JEP in the linked discussion. PR discussion should be limited to proofing the content of the PR and the PR proposal inital comment*
+
+## Abstract
+
+\<copy from JEP>
+
+## Implementation Survey
+
+*Omit this section if not relevant*
+
+Provide a minimal demonstration of how the proposed functionality would be implemented for each programming language.
+Include links to any proposed dependencies. This is to ensure that each language can support the proposed functionality, allows for
+the review of any additional dependencies that would need to be included with each implementation, provides reference for implementers,
+and ensures that each proposed implementation in each language has consistent behaviour across all languages.
+
+
+### Javascript/Typescript
+
+```typescript
+```
+
+### NodeJS
+
+```nodejs
+```
+
+### Python
+
+```python3
+```
+
+### C/C++
+
+```c++
+```
+
+### C#
+
+```c#
+```
+
+### PHP
+
+```php
+```
+
+### Java
+
+```java
+```
+
+### Rust
+
+```rust
+```
+
+### Go
+
+```go
+```
+
+### Lua
+
+```lua
+```

.github/workflows/test_validate.yaml

@@ -0,0 +1,32 @@
+name: Validate tests
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  # https://code.dblock.org/2021/09/03/generating-task-matrix-by-looping-over-repo-files-with-github-actions.html
+  list-tests:
+    runs-on: ubuntu-latest
+    outputs:
+      matrix: ${{ steps.set-matrix.outputs.matrix }}
+    steps:
+      - uses: actions/checkout@v2
+      - id: set-matrix
+        run: echo "::set-output name=matrix::$(ls grammar/*.json functions/*.json | jq -R -s -c 'split("\n")[:-1]')"
+  validate:
+    needs: list-tests
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        manifest: ${{ fromJson(needs.list-tests.outputs.matrix) }}
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v3
+        with:
+          cache: pip
+          cache-dependency-path: .github/workflows/validate_requirements.txt
+      - run: pip install -r .github/workflows/validate_requirements.txt
+      - name: Validate tests
+        run: "jsonschema test_schema.json -o pretty -i ${{ matrix.manifest }}"

.github/workflows/validate_requirements.txt

@@ -0,0 +1 @@
+jsonschema==4.4.0