Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`e2e/tests/utils/openApp.js` too specific

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript

Research direction

Start by reading e2e/tests/utils/openApp.js, especially resolveConfig and the configurationName check. Verify the behavior with configuration names such as ios.sim.debug and other intermediate naming formats; the work is done when debug configurations consistently use the debug app path without changing non-debug launches.

Written by the indexing model from the issue text.

Description

The openApp.js utility file is a great work around for local development; however, when bootstrapping / setting up Detox, the detoxrc.js file can refer to a config format such as ios.sim.debug or some other intermediate nomenclature between & .

As such, the conditional designed to check for a debug environment, only passes if it is the 2nd element of a "." split array.

I propose checking to see if the configuration name contains the word "debug" instead.

module.exports.openApp = async function openApp() {
  const config = await resolveConfig();
  if (config.configurationName.split(".").includes("debug")) {
    return await openAppForDebugBuild(platform);
  } else {
    return await device.launchApp({
      newInstance: true,
    });
  }
};
Dominant language
Java
Stars
34
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from expo/eas-tests-example

All issues in expo/eas-tests-example

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.