graphql-engine/server/tests-hspec/Test/HelloWorldSpec.hs

-- | A starting point feature test.
module Test.HelloWorldSpec (spec) where

import Harness.State (State)
import Harness.Test.Feature qualified as Feature
import Test.Hspec (SpecWith, it, shouldBe)

--------------------------------------------------------------------------------
-- Preamble

spec :: SpecWith State
spec = Feature.run [] tests

--------------------------------------------------------------------------------
-- Tests

tests :: Feature.Options -> SpecWith State
tests _opts = it "No-op" \_ -> do
  () `shouldBe` ()
Create integration testing environment (close hasura/graphql-engine#7752) dupe of @chrisdone's work https://github.com/hasura/graphql-engine-mono/pull/2829 with a branch rename PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2901 Co-authored-by: Chris Done <11019+chrisdone@users.noreply.github.com> GitOrigin-RevId: 8381e53a18242b75d7e17b18a2ba3b2d99dd1322 2021-11-17 22:50:39 +03:00			`-- \| A starting point feature test.`
Add README.md to tests-hspec and reorganize module namespace PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3421 GitOrigin-RevId: 8802d7e6a360edee62011ef371cc8930f36b25b1 2022-01-21 10:48:27 +03:00			`module Test.HelloWorldSpec (spec) where`
Create integration testing environment (close hasura/graphql-engine#7752) dupe of @chrisdone's work https://github.com/hasura/graphql-engine-mono/pull/2829 with a branch rename PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2901 Co-authored-by: Chris Done <11019+chrisdone@users.noreply.github.com> GitOrigin-RevId: 8381e53a18242b75d7e17b18a2ba3b2d99dd1322 2021-11-17 22:50:39 +03:00
Auto-launch graphql-engine (close hasura/graphql-engine#7801, hasura/graphql-engine#7827 ) Dupe of https://github.com/hasura/graphql-engine-mono/pull/2853 with branch renamed so it doesn't break a tool. prev pr: https://github.com/hasura/graphql-engine-mono/pull/2911 next pr: https://github.com/hasura/graphql-engine-mono/pull/2922 This implements https://github.com/hasura/graphql-engine/issues/7801 Some points to keep in mind for review: * How state is passed to the tests. Do we like how this works? * I quite like it, with the opaque type [`State`](https://github.com/hasura/graphql-engine-mono/blob/68f33051ca6373c42988e78d069eea2a135dc190/server/tests-hspec/Harness/State.hs#L17), we can avoid churn when adding things. * The [setup/teardown](https://github.com/hasura/graphql-engine-mono/blob/68f33051ca6373c42988e78d069eea2a135dc190/server/tests-hspec/Spec.hs#L19-L31) seems clean. * By using hspec's own means to pass and denote context, we avoid "getting new ideas" for how to structure the tests -- we use a standard. Hopefully, that means the tests' structure rarely change. * The various flags passed in the [ServeOptions](https://github.com/hasura/graphql-engine-mono/blob/68f33051ca6373c42988e78d069eea2a135dc190/server/tests-hspec/Harness/Constants.hs#L123) - if there are any causes for concern, raise them here. My thinking is that, there are lots. I've picked some "sane" defaults (mostly empty). The tests pass. I think as we add more complex tests, these flags will be scrutinised and updated as needed. I think it's valuable that all flags are explicitly listed here, though. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2921 GitOrigin-RevId: 2c2e70bf784ef571a48509a7e5006fd0f48773b5 2021-11-23 21:15:17 +03:00			`import Harness.State (State)`
Add README.md to tests-hspec and reorganize module namespace PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3421 GitOrigin-RevId: 8802d7e6a360edee62011ef371cc8930f36b25b1 2022-01-21 10:48:27 +03:00			`import Harness.Test.Feature qualified as Feature`
Prepare test suite for remote servers tests ## Description This PR adds all the scaffolding for tests that require remote servers. It is mostly a refactor of `Feature`; where we listed for each test a list of individual backends, we now provide a list of `Context`s, that allows for tests to specify not only how it should be setup, but also what state needs to be carried around throughout the test. This will be useful when launching custom remote servers. Additionally, this PR: - cleans the way we generate logs in the engine as part of the tests - cleans the cabal file - introduce a few more helpers for sending commands to the engine (such as `postMetadata_`) - allows for headers in queries sent to the engine (to support permissions tests) - adds basic code to start / stop a "remote" server This PR is a pre-requisite of #3567. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3573 Co-authored-by: jkachmar <8461423+jkachmar@users.noreply.github.com> GitOrigin-RevId: 05f808c6b85729dbb3ea6648c3e10a3c16b641ef 2022-02-14 20:24:24 +03:00			`import Test.Hspec (SpecWith, it, shouldBe)`
Create integration testing environment (close hasura/graphql-engine#7752) dupe of @chrisdone's work https://github.com/hasura/graphql-engine-mono/pull/2829 with a branch rename PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2901 Co-authored-by: Chris Done <11019+chrisdone@users.noreply.github.com> GitOrigin-RevId: 8381e53a18242b75d7e17b18a2ba3b2d99dd1322 2021-11-17 22:50:39 +03:00
			`--------------------------------------------------------------------------------`
			`-- Preamble`

Auto-launch graphql-engine (close hasura/graphql-engine#7801, hasura/graphql-engine#7827 ) Dupe of https://github.com/hasura/graphql-engine-mono/pull/2853 with branch renamed so it doesn't break a tool. prev pr: https://github.com/hasura/graphql-engine-mono/pull/2911 next pr: https://github.com/hasura/graphql-engine-mono/pull/2922 This implements https://github.com/hasura/graphql-engine/issues/7801 Some points to keep in mind for review: * How state is passed to the tests. Do we like how this works? * I quite like it, with the opaque type [`State`](https://github.com/hasura/graphql-engine-mono/blob/68f33051ca6373c42988e78d069eea2a135dc190/server/tests-hspec/Harness/State.hs#L17), we can avoid churn when adding things. * The [setup/teardown](https://github.com/hasura/graphql-engine-mono/blob/68f33051ca6373c42988e78d069eea2a135dc190/server/tests-hspec/Spec.hs#L19-L31) seems clean. * By using hspec's own means to pass and denote context, we avoid "getting new ideas" for how to structure the tests -- we use a standard. Hopefully, that means the tests' structure rarely change. * The various flags passed in the [ServeOptions](https://github.com/hasura/graphql-engine-mono/blob/68f33051ca6373c42988e78d069eea2a135dc190/server/tests-hspec/Harness/Constants.hs#L123) - if there are any causes for concern, raise them here. My thinking is that, there are lots. I've picked some "sane" defaults (mostly empty). The tests pass. I think as we add more complex tests, these flags will be scrutinised and updated as needed. I think it's valuable that all flags are explicitly listed here, though. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2921 GitOrigin-RevId: 2c2e70bf784ef571a48509a7e5006fd0f48773b5 2021-11-23 21:15:17 +03:00			`spec :: SpecWith State`
Prepare test suite for remote servers tests ## Description This PR adds all the scaffolding for tests that require remote servers. It is mostly a refactor of `Feature`; where we listed for each test a list of individual backends, we now provide a list of `Context`s, that allows for tests to specify not only how it should be setup, but also what state needs to be carried around throughout the test. This will be useful when launching custom remote servers. Additionally, this PR: - cleans the way we generate logs in the engine as part of the tests - cleans the cabal file - introduce a few more helpers for sending commands to the engine (such as `postMetadata_`) - allows for headers in queries sent to the engine (to support permissions tests) - adds basic code to start / stop a "remote" server This PR is a pre-requisite of #3567. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3573 Co-authored-by: jkachmar <8461423+jkachmar@users.noreply.github.com> GitOrigin-RevId: 05f808c6b85729dbb3ea6648c3e10a3c16b641ef 2022-02-14 20:24:24 +03:00			`spec = Feature.run [] tests`
Create integration testing environment (close hasura/graphql-engine#7752) dupe of @chrisdone's work https://github.com/hasura/graphql-engine-mono/pull/2829 with a branch rename PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2901 Co-authored-by: Chris Done <11019+chrisdone@users.noreply.github.com> GitOrigin-RevId: 8381e53a18242b75d7e17b18a2ba3b2d99dd1322 2021-11-17 22:50:39 +03:00
			`--------------------------------------------------------------------------------`
			`-- Tests`

Prepare test suite for remote servers tests ## Description This PR adds all the scaffolding for tests that require remote servers. It is mostly a refactor of `Feature`; where we listed for each test a list of individual backends, we now provide a list of `Context`s, that allows for tests to specify not only how it should be setup, but also what state needs to be carried around throughout the test. This will be useful when launching custom remote servers. Additionally, this PR: - cleans the way we generate logs in the engine as part of the tests - cleans the cabal file - introduce a few more helpers for sending commands to the engine (such as `postMetadata_`) - allows for headers in queries sent to the engine (to support permissions tests) - adds basic code to start / stop a "remote" server This PR is a pre-requisite of #3567. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3573 Co-authored-by: jkachmar <8461423+jkachmar@users.noreply.github.com> GitOrigin-RevId: 05f808c6b85729dbb3ea6648c3e10a3c16b641ef 2022-02-14 20:24:24 +03:00			`tests :: Feature.Options -> SpecWith State`
			`tests _opts = it "No-op" \_ -> do`
			() `shouldBe` ()