Cannot read properties of undefined (reading 'type')

Cannot read properties of undefined (reading 'type')

eachValueMatches

eachKeyMatches

mockService.url

record-deployment

can-i-deploy

can-i-deploy

record-deployment

--environment test

pact-broker publish --consumer-app-version=<<SHA goes here>> ...

@pact-foundation/pact

Ask and you shall receive v7.3.0 on the way out that both allows a dynamic port (see e2e and typescript examples) and will return the full complement of Pact options from setup().

import {
  HttpLink,
  InMemoryCache,
  ApolloClient,
  NormalizedCacheObject,
} from '@apollo/client';
import { PactTestServerConfig } from '@/utils/pact-constants';
import fetch from 'cross-fetch';

let client: ApolloClient<NormalizedCacheObject>;

global.fetch = fetch;

export const setupPactTests = () => {
  const client = new ApolloClient({
    cache: new InMemoryCache({ addTypename: false }),
    link: new HttpLink({
      uri: `<http://127.0.0.1>:${PactTestServerConfig.Port}/graphql`,
      fetch,
    }),
  });

  return client;
};

export function getApolloClient(): ApolloClient<NormalizedCacheObject> {
  if (!client) {
    client = setupPactTests();
  }
  return client;
}

can-i-merge

Type mismatch: Expected '{"contractVersion":2,"status":{"code":"STUDY_NOT_APPLICABLE","text":"Study processing failed during looking up raw results"},"fhirJson":null,"study":{"uid":"65f4205422a8e1c5282a10278d82baf7aa692da6cd2f4474a1a591d491e14800","artifacts":[{"name":"Annalise-ctc-d6f80baf-c696-4e57-95db-43e0fe0b7a3d.log","documentType":"text/log","groupCode":"annalise-ctc-log","trackingUIDs":["262d7217-0f85-4b64-aebf-1bbaa6759701"]}],"series":null}}' (String) to be the same type as {"contractVersion":101,"fhirJson":null,"status":{"code":"some string","text":"some string"},"study":{"artifacts":[{"documentType":"some string","groupCode":"some string","name":"some string","trackingUIDs":["some string"]}],"series":null,"uid":"some string"}} (Object)

SyntaxError: Cannot use import statement outside a module

      4 |
      5 | const nock = require('nock');
    > 6 | const PactV3 = require('../../../node_modules/@pact-foundation/pact')
● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see <https://jestjs.io/docs/ecmascript-modules> for how to enable it.
     • If you are trying to use TypeScript, see <https://jestjs.io/docs/getting-started#using-typescript>
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    <https://jestjs.io/docs/configuration>
    For information about custom transformations, see:
    <https://jestjs.io/docs/code-transformation>

    Details:

    C:\Users\DanielB\source\repos\Core.Website.v2\node_modules\@pact-foundation\pact\node_modules\axios\index.js:1
    ({"Object.<anonymous>":function(module,exports,require,_dirname,_filename,jest){import axios from './lib/axios.js';
                                                                                      ^^^^^^

pact-js

jest-pact

SuperTest

Pact between Jest-Consumer-Example and Provider
    with 30000 ms timeout for Pact

Pact verification failed - expected interactions did not match actual.

debug

trace

const url = '/path/to/endpoint'

pactWith(
    {
        consumer: "Jest-Consumer-Example",
        provider: "Provider",
        logLevel: LOG_LEVEL as LogLevel,
        pactfileWriteMode: 'merge',
    },
    (provider) => {
        describe('The API', () => { 
            const itemExample = {
                "NumberField": 3,
            }     
            const EXPECTED_BODY = {
                results: eachLike(itemExample)
            }
            const itemSuccessResponse = {
                status: 200,
                body: EXPECTED_BODY,
            }
            const itemRequest = {
                uponReceiving: 'a request for a thing',
                withRequest: {
                    method: 'GET' as HTTPMethods,
                    path: url,
                }
            }

            let agent: SuperAgentTest
            beforeEach(async () => {
                agent = await AuthHelper.createAgent()
                const interaction: InteractionObject = {
                    state: 'I have a thing',
                    ...itemRequest,
                    willRespondWith: itemSuccessResponse,
                }
                return provider.addInteraction(interaction)
            })
            it('returns a successful body', () => {
                return agent.get(`${endpointPath}`)
                    .then((item) => {
                        console.log(item)
                    })
            })
        })
    }
)

make ci PACT_BROKER_BASE_URL="..." PACT_BROKER_TOKEN="..." PACT_PROVIDER="..."

Specified pact file 'pacts' does not exist. This sometimes indicates one of the arguments has been specified with the wrong name and has been incorrectly identified as a file path. If you are using Docker, check that you have mounted the pact file or directory into the container correctly using

make: *** [publish_pacts] Error 1

Content-Type: application/x-ndjson

willRespondWith

{\"value\":

{ \"value\": {}, \"pact:matcher:type\": \"type\" }

Content-Type

application/x-ndjson

application/json

MatchersV3

spec: 3

Matchers

eachLike

MatchersV3

Matchers

body-parser

Client error: 403 Forbidden Failed to create session

pactflow-ai status

15:08:15  [15:08:15.632] DEBUG (676): pact@13.2.0: mock service started on port: 8081
15:08:45  [15:08:45.635] ERROR (677): pact@13.2.0: The pact mock service doesn't appear to be running
15:08:45    - Please check the logs above to ensure that there are no pact service startup failures
15:08:45    - Please check that pact lifecycle methods are called in the correct order (setup() needs to be called before this method)
15:08:45    - Please check that your test code waits for the promises returned from lifecycle methods to complete before calling the next one
15:08:45    - To learn more about what is happening during your pact run, try setting logLevel: 'DEBUG'

"@pact-foundation/pact": "13.2.0",

then

error

finally

pact.publishPacts(opts)
        .then(function() {
          console.log(`Published pact successfully. It should be updated on ${brokerUrl}.`);
        })
        .catch(function(err) {
          console.error('Failed to publish pact:', err);
        })
        .finally(function() {
          console.log('i am in finally');
        });

[16:06:01.224] INFO (89029): pact-node@10.18.0: Publishing Pacts to Broker
[16:06:01.225] INFO (89029): pact-node@10.18.0: Publishing pacts to broker at: https://*****.<http://pactflow.io|pactflow.io>

pact-js

node_modules

4010

netstat