Using computable names in the jest describe/it results in Jest Runner not picking up the test

[MattBidewell]

(could be more of a feature enhancement rather than a bug)

👋🏻 hey folks!

Found a scenario where using the computed name of path.basename(__filename) will result in the test being skipped due to it not be found when running run.

Example:

import path from 'path';

describe(path.basename(__filename), () => {
  it('doesnt execute', () => {
    expect(true).toBe(true);
  });
});

describe('does work', () => {
  it('does execute', () => {
    expect(true).toBe(true);
  })
})

Repo with example: https://github.com/MattBidewell/jest-runner-name-bug

When running run above the test using the computed describe name:

When running run above the standard describe name:

I suspect we might need to potentially do a replace on the name value before we execute the command in the terminal.