Introduction for developers. How to fork project and run tests without errors? #984

gustawdaniel · 2020-06-06T16:28:29Z

gustawdaniel
Jun 6, 2020

I forked this repo. Run

npm i

npm run test

And have some problems. Can anyone show how to:

Install project on ubuntu?
Run tests without errors?

Details of problems listed here:

 FAIL  src/lib/watcher/index.spec.ts
  ● Test suite failed to run

    src/lib/watcher/index.spec.ts:3:31 - error TS2307: Cannot find module '../../../dist/lib/watcher' or its corresponding type declarations.

    3 import { createWatcher } from '../../../dist/lib/watcher'
                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    src/lib/watcher/index.spec.ts:31:18 - error TS7006: Parameter 'e' implicitly has an 'any' type.

    31         events: (e) => {

and

 FAIL  src/lib/build/bundle.spec.ts (18.397 s)
  ✕ should not bundle typescript (28 ms)
  ✕ should not bundle any of the cli (2 ms)
  deployment=heroku
    ✎ todo checks that the start script points to the build output (bundle true)
    ✎ todo checks that the start script points to the build output (bundle false)
    ✎ todo checks that the package engines field is correctly set

  ● should not bundle typescript

    File /home/daniel/pro/ocr/nexus/dist/index.js does not exist.

      67 |   const worktimeTesttimePluginPaths = getWorktimeAndTesttimePluginPaths(opts.base, opts.plugins)
      68 | 
    > 69 |   const { fileList, reasons } = await fileTrace([opts.entrypoint], {
         |                                                ^
      70 |     ts: true,
      71 |     mixedModules: true,
      72 |     base: opts.base,

      at Job.emitDependency (node_modules/@zeit/node-file-trace/src/node-file-trace.js:242:34)
      at node_modules/@zeit/node-file-trace/src/node-file-trace.js:31:18
          at Array.map (<anonymous>)
      at Object.module.exports [as default] (node_modules/@zeit/node-file-trace/src/node-file-trace.js:27:27)
      at Object.traceFiles (src/lib/build/bundle.ts:69:48)
      at Object.<anonymous> (src/lib/build/bundle.spec.ts:9:29)

  ● should not bundle any of the cli

    File /home/daniel/pro/ocr/nexus/dist/index.js does not exist.

      67 |   const worktimeTesttimePluginPaths = getWorktimeAndTesttimePluginPaths(opts.base, opts.plugins)
      68 | 
    > 69 |   const { fileList, reasons } = await fileTrace([opts.entrypoint], {
         |                                                ^
      70 |     ts: true,
      71 |     mixedModules: true,
      72 |     base: opts.base,

      at Job.emitDependency (node_modules/@zeit/node-file-trace/src/node-file-trace.js:242:34)
      at node_modules/@zeit/node-file-trace/src/node-file-trace.js:31:18
          at Array.map (<anonymous>)
      at Object.module.exports [as default] (node_modules/@zeit/node-file-trace/src/node-file-trace.js:27:27)
      at Object.traceFiles (src/lib/build/bundle.ts:69:48)
      at Object.<anonymous> (src/lib/build/bundle.spec.ts:20:27)

also

  ✕ detects yarn as package manager (13 ms)
  ● detects yarn as package manager

Finally

Test Suites: 7 failed, 8 passed, 15 total
Tests:       7 failed, 9 todo, 91 passed, 107 total
Snapshots:   1 failed, 36 obsolete, 63 passed, 64 total
Time:        43.896 s
Ran all test suites.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test: `LOG_PRETTY=true DEBUG=true jest --verbose --testTimeout 360000`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/daniel/.npm/_logs/2020-06-06T16_23_36_112Z-debug.log

gustawdaniel · 2020-06-06T16:38:14Z

gustawdaniel
Jun 6, 2020
Author

I know that there id DEVELOPMENT.md

but event if i run

yarn test:unit

I see

 FAIL  src/lib/build/bundle.spec.ts
  ✕ should not bundle typescript (29 ms)
  ✕ should not bundle any of the cli (2 ms)
  deployment=heroku
    ✎ todo checks that the start script points to the build output (bundle true)
    ✎ todo checks that the start script points to the build output (bundle false)
    ✎ todo checks that the package engines field is correctly set

  ● should not bundle typescript

    File /home/daniel/pro/ocr/nexus/dist/index.js does not exist.

      67 |   const worktimeTesttimePluginPaths = getWorktimeAndTesttimePluginPaths(opts.base, opts.plugins)
      68 | 
    > 69 |   const { fileList, reasons } = await fileTrace([opts.entrypoint], {
         |                                                ^
      70 |     ts: true,
      71 |     mixedModules: true,
      72 |     base: opts.base,

      at Job.emitDependency (node_modules/@zeit/node-file-trace/src/node-file-trace.js:242:34)
      at node_modules/@zeit/node-file-trace/src/node-file-trace.js:31:18
          at Array.map (<anonymous>)
      at Object.module.exports [as default] (node_modules/@zeit/node-file-trace/src/node-file-trace.js:27:27)
      at Object.traceFiles (src/lib/build/bundle.ts:69:48)
      at Object.<anonymous> (src/lib/build/bundle.spec.ts:9:29)

  ● should not bundle any of the cli

    File /home/daniel/pro/ocr/nexus/dist/index.js does not exist.

      67 |   const worktimeTesttimePluginPaths = getWorktimeAndTesttimePluginPaths(opts.base, opts.plugins)
      68 | 
    > 69 |   const { fileList, reasons } = await fileTrace([opts.entrypoint], {
         |                                                ^
      70 |     ts: true,
      71 |     mixedModules: true,
      72 |     base: opts.base,

      at Job.emitDependency (node_modules/@zeit/node-file-trace/src/node-file-trace.js:242:34)
      at node_modules/@zeit/node-file-trace/src/node-file-trace.js:31:18
          at Array.map (<anonymous>)
      at Object.module.exports [as default] (node_modules/@zeit/node-file-trace/src/node-file-trace.js:27:27)
      at Object.traceFiles (src/lib/build/bundle.ts:69:48)
      at Object.<anonymous> (src/lib/build/bundle.spec.ts:20:27)

and

 FAIL  src/lib/watcher/index.spec.ts
  ● Test suite failed to run

    src/lib/watcher/index.spec.ts:3:31 - error TS2307: Cannot find module '../../../dist/lib/watcher' or its corresponding type declarations.

    3 import { createWatcher } from '../../../dist/lib/watcher'
                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    src/lib/watcher/index.spec.ts:31:18 - error TS7006: Parameter 'e' implicitly has an 'any' type.

    31         events: (e) => {
                        ~

Finally

Test Suites: 2 failed, 9 passed, 11 total
Tests:       2 failed, 9 todo, 92 passed, 103 total
Snapshots:   64 passed, 64 total
Time:        11.383 s
Ran all test suites matching /src/i.
error Command failed with exit code 1.
error Command failed with exit code 1.

0 replies

gustawdaniel · 2020-09-05T12:56:40Z

gustawdaniel
Sep 5, 2020
Author

My tests still failing:

npm run test

> [email protected] test /home/daniel/pro/cm/local/nexus
> cross-env FORCE_COLOR=3 LOG_PRETTY=true DEBUG=true jest --testTimeout 1200000 --forceExit

sh: 1: cross-env: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
> [email protected] postinstall /home/daniel/pro/cm/local/nexus/node_modules/core-js

> @apollo/[email protected] postinstall /home/daniel/pro/cm/local/nexus/node_modules/@apollo/protobufjs
> node scripts/postinstall


> [email protected] postinstall /home/daniel/pro/cm/local/nexus
> node scripts/postinstall


│  WARNING from nexus
│  WARNING from nexus
│  WARNING from nexus
│ 
│  nexus bundles graphql and @nexus/schema dependencies.
│  So please uninstall the ones you have installed or you
│  may encounter problems.
│  
│  Run the following commands to fix this issue
 FAIL  src/lib/build/bundle.spec.ts (19.465 s)
  ● should not bundle typescript

      at Object.traceFiles (src/lib/build/bundle.ts:68:39)

       |          message: 'Boolean cannot represent a non boolean value: "wrong type"',
       |          }
       |              column: 3
 FAIL  src/lib/layout/index.spec.ts (22.198 s)
       |             }
  23 ▲ nexus:e2eTesting create prisma app
2413 — nexus:e2eTesting setup
       |               localNexus: null,
      at PipeSocket.<anonymous> (src/lib/e2e-testing.ts:209:23)
      at UnixTerminal.Terminal.emit (node_modules/node-pty/src/terminal.ts:149:30)
      at onexit (node_modules/node-pty/src/unixTerminal.ts:101:12)

 › 2 snapshots obsolete.
   • create prisma app: introspection 1
   • create prisma app: query 1
  30 ▲ nexus:e2e:kitchenSink create app
internal/modules/cjs/loader.js:969
  throw err;
  ^

Error: Cannot find module '/home/daniel/pro/cm/local/nexus/dist/cli/main'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
    at Function.Module._load (internal/modules/cjs/loader.js:842:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
    at internal/main/run_main_module.js:17:47 {
}
  ^

Error: Cannot find module '/home/daniel/pro/cm/local/nexus/dist/cli/main'
   • kitchen sink: built app query 1
       |               runningLocalTool: false,
       |               },
       |               project: null
       |             }
   3 — nexus:glocal execLayout done
   6 ● nexus:cli:create:app Installing dependencies  --  nexusVersion: '0.26.1'
Error: The following command failed to complete successfully:

    

It output on stdout (null = not spawned in pipe mode):
    at createCommandError (/home/daniel/.npm/_npx/54862/lib/node_modules/nexus/dist/lib/process/index.js:142:19)
    at ChildProcess.<anonymous> (/home/daniel/.npm/_npx/54862/lib/node_modules/nexus/dist/lib/process/index.js:76:31)
    at Object.onceWrapper (events.js:422:26)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.EventEmitter.emit (domain.js:482:12)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)
    at onErrorNT (internal/child_process.js:469:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  exitCode: null,
  signal: null,
  stderr: '',
  stdout: ''
}
  16 — nexus exiting  --  beforeExitersCount: 0
 FAIL  test/e2e/create-prisma-app.test.ts (47.613 s)
  ● create prisma app

    command "npx nexus@latest" exited 1

      207 | 
      208 |       if (exitCode !== 0) {
    > 209 |         const error = new Error(`command "${command} ${args.join(' ')}" exited ${exitCode}`)
          |                       ^
      210 |         Object.assign(error, result)
      211 |         sub.error(error)
      212 |       } else {

      at PipeSocket.<anonymous> (src/lib/e2e-testing.ts:209:23)
      at UnixTerminal.Terminal.emit (node_modules/node-pty/src/terminal.ts:149:30)
      at onexit (node_modules/node-pty/src/unixTerminal.ts:101:12)

 › 2 snapshots obsolete.
   • create prisma app: introspection 1
   • create prisma app: query 1
 FAIL  test/e2e/kitchen-sink.test.ts (47.762 s)
  ● kitchen sink

    command "npx nexus@latest" exited 1

      207 | 
      208 |       if (exitCode !== 0) {
    > 209 |         const error = new Error(`command "${command} ${args.join(' ')}" exited ${exitCode}`)
          |                       ^
      210 |         Object.assign(error, result)
      211 |         sub.error(error)
      212 |       } else {

      at PipeSocket.<anonymous> (src/lib/e2e-testing.ts:209:23)
      at UnixTerminal.Terminal.emit (node_modules/node-pty/src/terminal.ts:149:30)
      at onexit (node_modules/node-pty/src/unixTerminal.ts:101:12)

 › 16 snapshots obsolete.
   • kitchen sink: built app addToContext query 2
   • kitchen sink: built app backing type query 1
   • kitchen sink: built app backing type query 2
   • kitchen sink: built app introspection 1
   • kitchen sink: built app introspection 2
   • kitchen sink: built app query 1
   • kitchen sink: built app query 2
   • kitchen sink: introspection 1
   • kitchen sink: introspection 2
   • kitchen sink: query 1
   • kitchen sink: query 2
Snapshot Summary
 › 1 snapshot failed from 1 test suite. Inspect your code changes or run `npm test -- -u` to update them.
 › 36 snapshots obsolete from 4 test suites. To remove them all, run `npm test -- -u`.
   ↳ test/system/create-prisma-app.test.ts
       • create prisma app: introspection 1
       • create prisma app: query 1
   ↳ test/system/kitchen-sink.test.ts
       • kitchen sink: addToContext query 1
       • kitchen sink: addToContext query 2
       • kitchen sink: backing type query 1
       • kitchen sink: backing type query 2
       • kitchen sink: built app addToContext query 1
       • kitchen sink: built app addToContext query 2
       • kitchen sink: built app backing type query 1
       • kitchen sink: built app backing type query 2
       • kitchen sink: built app introspection 1
       • kitchen sink: built app introspection 2
       • kitchen sink: built app query 1
       • kitchen sink: built app query 2
       • kitchen sink: introspection 1
       • kitchen sink: introspection 2
       • kitchen sink: query 1
       • kitchen sink: query 2
   ↳ test/e2e/create-prisma-app.test.ts
       • create prisma app: introspection 1
       • create prisma app: query 1
   ↳ test/e2e/kitchen-sink.test.ts
       • kitchen sink: addToContext query 1
       • kitchen sink: addToContext query 2
       • kitchen sink: backing type query 1
       • kitchen sink: backing type query 2
       • kitchen sink: built app addToContext query 1
       • kitchen sink: built app addToContext query 2
       • kitchen sink: built app backing type query 1
       • kitchen sink: built app backing type query 2
       • kitchen sink: built app introspection 1
       • kitchen sink: built app introspection 2
       • kitchen sink: built app query 1
       • kitchen sink: built app query 2
       • kitchen sink: introspection 1
       • kitchen sink: introspection 2
       • kitchen sink: query 1
       • kitchen sink: query 2

Test Suites: 8 failed, 12 passed, 20 total
Tests:       8 failed, 9 todo, 140 passed, 157 total
Snapshots:   1 failed, 36 obsolete, 96 passed, 97 total
Time:        48.719 s
Ran all test suites.
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test: `cross-env FORCE_COLOR=3 LOG_PRETTY=true DEBUG=true jest --testTimeout 1200000 --forceExit`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/daniel/.npm/_logs/2020-09-05T12_53_52_306Z-debug.log

I am on master of this project.

Please for introduction for developers that want to create fork and introduced improvement to this package.

0 replies

gustawdaniel · 2020-09-05T13:21:25Z

gustawdaniel
Sep 5, 2020
Author

I found instruction:

https://github.com/graphql-nexus/nexus/blob/master/CONTRIBUTING.md

but even after installing yarn when I type: yarn test:unit I have failing tests:

PASS  src/runtime/server/handler-graphql.spec.ts
  18 ■ nexus:server:graphql An exception occurred in one of your resolver
       | error  {
       |          message: 'Cannot query field "bad" on type "Query".',
       |          locations: [
       |            {
       |              line: 1,
       |              column: 3
       |            }
       |          ],
       |          path: undefined,
       |          extensions: {
       |            code: 'GRAPHQL_VALIDATION_FAILED'
       |          }
       |        }
  27 ■ nexus:server:graphql An exception occurred in one of your resolver
       | error  {
       |          message: 'Variables must be provided as an Object where each property is a variable value. Perhaps look to see if an unparsed JSON string was provided.',
       |          locations: undefined,
       |          path: undefined,
       |          extensions: {
       |            code: 'INTERNAL_SERVER_ERROR'
       |          }
       |        }
 PASS  src/runtime/app.spec.ts
● nexus:server listening  --  url: 'http://localhost:7583/graphql'
 FAIL  src/lib/watcher/index.spec.ts
  ● Test suite failed to run

    src/lib/watcher/index.spec.ts:5:31 - error TS2307: Cannot find module '../../../dist/lib/watcher' or its corresponding type declarations.

    5 import { createWatcher } from '../../../dist/lib/watcher'
                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    src/lib/watcher/index.spec.ts:32:18 - error TS7006: Parameter 'e' implicitly has an 'any' type.

    32         events: (e) => {
                        ~

 PASS  src/lib/add-to-context-extractor/extractor.spec.ts (21.814 s)

Test Suites: 3 failed, 13 passed, 16 total
Tests:       3 failed, 9 todo, 141 passed, 153 total
Snapshots:   97 passed, 97 total
Time:        22.58 s, estimated 44 s
Ran all test suites matching /src/i.
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Introduction for developers. How to fork project and run tests without errors? #984

{{title}}

Replies: 3 comments

{{title}}

{{title}}

{{title}}

Select a reply

Introduction for developers. How to fork project and run tests without errors? #984

gustawdaniel Jun 6, 2020

Replies: 3 comments

gustawdaniel Jun 6, 2020 Author

gustawdaniel Sep 5, 2020 Author

gustawdaniel Sep 5, 2020 Author

gustawdaniel
Jun 6, 2020

gustawdaniel
Jun 6, 2020
Author

gustawdaniel
Sep 5, 2020
Author

gustawdaniel
Sep 5, 2020
Author