ephemeraHQ / message-kit

MessageKit
https://messagekit.ephemerahq.com/
MIT License
22 stars 2 forks source link

Feature request: Improved testing #114

Open fabriguespe opened 18 hours ago

fabriguespe commented 18 hours ago

Add testing scenarios for xmtpClient. On going, asked @rygine for help

fabriguespe commented 18 hours ago

https://github.com/ephemeraHQ/message-kit/pull/108

saulmc commented 14 hours ago

@fabriguespe will this fix skills.ts not loading during runtime tests? MessageKit currently looks for a js file in dist/

fabriguespe commented 13 hours ago

No this is for testing xmtpClient.

Tracking your issue here now. https://github.com/ephemeraHQ/message-kit/issues/120

fabriguespe commented 13 hours ago
-jest[ts-jest-transformer] (WARN) Got a `.js` file to compile while `allowJs` option is not set to `true` (file: /Users/fabrizioguespe/DevRel/message-kit/node_modules/@xmtp/grpc-api-client/dist/src/index.js). To fix this:
  - if you want TypeScript to process JS files, set `allowJs` to `true` in your TypeScript config (usually tsconfig.json)
  - if you do not want TypeScript to process your `.js` files, in your Jest config change the `transform` key which value is `ts-jest` so that it does not match `.js` files anymore
 FAIL  src/tests/Client.test.ts
  ● 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

cc @rygine