Jest test finder can get misled by irrelevant "describe" blocks

[johannes-mueller]

Thanks @ktfleming for reporting this. Sorry, I accidentally transformed the issue you reported into a pull request. But anyway. This PR seems to fix it.

Hey, I'm really finding this package useful, thanks for creating it!

I've found that (test-cockpit-npm-jest--find-current-test) doesn't handle the following case:

describe("outer", () => {
  describe("middle", () => {
  });

  it("foo", async () => {
    expect(2).toBe(2); // HERE
  });
});

If I put point on the line marked // HERE and evaluate (test-cockpit-npm-jest--find-current-test), the output is "middle foo", rather than the expected "outer foo". It seems that it's looking for the closest preceding "describe" via search-backward-regexp, rather than looking for the "describe" that contains the test at point.

I do see you have an open issue #7 for looking into tree-sitter which I imagine could help with this by allowing you to look at only the parent node of the current node.

[ktfleming]

@johannes-mueller It's working for me, thanks so much for the quick fix!