Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Half of the test cases in a test suite in RP is displaying no results #33

Open
mtrejo-evgo opened this issue May 20, 2024 · 18 comments
Open

Comments

@mtrejo-evgo
Copy link

Save log with tempId abcd {
  promiseStart: Promise {
    {
      id: 'REDACTED',
      uniqueId: 'REDACTED'
    }
  },
  realId: 'REDACTED',
  children: [ 'abce' ],
  finishSend: false,
  promiseFinish: Promise { <pending> },
  resolveFinish: [Function (anonymous)],
  rejectFinish: [Function (anonymous)]
Finish test item with tempId abcd { endTime: 1715989367638, status: 'failed' }
@kobenguyent
Copy link
Owner

Hey, is it possible if could provide the screenshot? Ofc, censoring your sensitive information.

@mtrejo-evgo
Copy link
Author

Screenshot 2024-05-20 at 9 42 00 AM

@kobenguyent
Copy link
Owner

Hmm, strange! Did you run with codeceptjs run or run-workers?

@mtrejo-evgo
Copy link
Author

yarn test --grep

@mtrejo-evgo
Copy link
Author

mtrejo-evgo commented May 23, 2024

I think yarn test runs "codeceptjs run --verbose"

@kobenguyent
Copy link
Owner

Supposedly, the codeceptjs run or codeceptjs run-workers should give us the same results. May I know if there is any reason that prevents you from using run-workers? I'm asking because the issue happens with run command would be in lower priority as mostly, I think, we would essentially use run-workers to execute tests in the real world scenarios and run command is useful to debug a specific test, for instance.

@mtrejo-evgo
Copy link
Author

Hey @kobenguyent, I've run it with run-workers now, I'm seeing the same results.

@kobenguyent
Copy link
Owner

Hey @mtrejo-evgo would be nice if you could provide a minimal repo where I could reproduce the issue.

@mtrejo-evgo
Copy link
Author

@kobenguyent, we don't have a way of providing a sample of our repo without exposing our private info.

@mtrejo-evgo
Copy link
Author

is there anything explicit that we could share?

@kobenguyent
Copy link
Owner

Ah, is it possible that you could add DEBUG=* before the command like DEBUG=* codeceptjs run --verbose. That would give us more information. Hopefully you could see any errors from the console logs.

@mtrejo-evgo
Copy link
Author

Here's the results

From running codeceptjs:


 follow-redirects options {
  maxRedirects: 21,
  maxBodyLength: 10485760,
  protocol: 'https:',
  path: '/api/v1/project/item/abcd’,
  method: 'PUT',
  headers: {
    Accept: 'application/json, text/plain, */*',
    'Content-Type': 'application/json',
    'User-Agent': 'NodeJS',
    Authorization: 'bearer REDACTED’,
    'Content-Length': 95
  },
  agent: undefined,
  agents: { http: undefined, https: undefined },
  auth: undefined,
  hostname: 'saas.reportportal.io',
  port: null,
  nativeProtocols: {
    'http:': {
      _connectionListener: [Function: connectionListener],
      METHODS: [Array],
      STATUS_CODES: [Object],
      Agent: [Function],
      ClientRequest: [Function: ClientRequest],
      IncomingMessage: [Function: IncomingMessage],
      OutgoingMessage: [Function: OutgoingMessage],
      Server: [Function: Server],
      ServerResponse: [Function: ServerResponse],
      createServer: [Function: createServer],
      validateHeaderName: [Function: __node_internal_],
      validateHeaderValue: [Function: __node_internal_],
      get: [Function: get],
      request: [Function: request],
      setMaxIdleHTTPParsers: [Function: setMaxIdleHTTPParsers],
      maxHeaderSize: [Getter],
      globalAgent: [Getter/Setter]
    },
    'https:': {
      Agent: [Function: Agent],
      globalAgent: [Agent],
      Server: [Function: Server],
      createServer: [Function: createServer],
      get: [Function: get],
      request: [Function: request]
    }
  }
} +6ms

From report portal:



{
    "id": 1234,
    "uuid": “abcd”,
    "name": “Create customer”,
    "codeRef": "",
    "parameters": [],
    "attributes": [],
    "type": "SUITE",
    "startTime": 1717004294038,
    "endTime": 1717004294039,
    "status": "FAILED",
    "statistics": {
        "executions": {},
        "defects": {
            "to_investigate": {
                "total": 1,
                "ti001": 1
            }
        }
    },
    "pathNames": {
        "launchPathName": {
            "name": "stg-testing",
            "number": 1
        }
    },
    "issue": {
        "issueType": "ti001",
        "autoAnalyzed": false,
        "ignoreAnalyzer": false,
        "externalSystemIssues": []
    },
    "hasChildren": false,
    "hasStats": true,
    "launchId": 0987654,
    "uniqueId": "a:1asdf2”,
    "testCaseId": "",
    "testCaseHash": 0,
    "patternTemplates": [],
    "path": “97665554”
}

@mtrejo-evgo
Copy link
Author

Hey @kobenguyent , do you still need anything from our side?

@kobenguyent
Copy link
Owner

kobenguyent commented Jun 27, 2024

@mtrejo-evgo would be nice to have a sample repo where I could replicate the issue. I'm still puzzled as I could not trace any issue with my test repo.

@mtrejo-evgo
Copy link
Author

@kobenguyent could we schedule a call with you sometime to share the repo so you can see the issue?

@kobenguyent
Copy link
Owner

@mtrejo-evgo sure. That'll be great!

@mtrejo-evgo
Copy link
Author

I'll reach out on slack to try to schedule

@kobenguyent
Copy link
Owner

after the debug session, we found the issue is that when test failed at hooks. No results are logging into RP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants