nightwatchjs/nightwatch-vscode

Issues

• Process failed: spawn /bin/sh ENOENT - when running tests

  #45 opened 2 months ago by MurzNN
  0

• Unable to successfully install extension

  #44 opened 7 months ago by Yashwanth-work
  0

• Test path not found

  #38 opened 7 months ago by xUrko
  1

• Uncaught Errors

  #39 opened 7 months ago by xUrko
  0

• Reset nwConfig before refreshing for a new one

  #42 opened 8 months ago by garg3133
  0

• Debugger doesn't appear to respect the --env CLI parameter and use per-environment globals overwriting default globals

  #40 opened 9 months ago by NWinocur
  4

• Users should be able to stop if tests cases are refreshing for a long time

  #24 opened 2 years ago by vaibhavsingh97
  0

• Publish Nightwatch to Open VSX

  #32 opened 2 years ago by omhomurlu
  0

• Users should be able to debug last failed tests

  #20 opened 2 years ago by vaibhavsingh97
  0

• Condition: Subset of tests

  #11 opened 2 years ago by vaibhavsingh97
  0

• Condition: Running single test

  #10 opened 2 years ago by vaibhavsingh97
  0

• Condition: Running tests from multiple files

  #13 opened 2 years ago by vaibhavsingh97
  0

• Displaying failures of the test on editor

  #14 opened 2 years ago by vaibhavsingh97
  0

• Displaying tests results in the Terminal

  #16 opened 2 years ago by vaibhavsingh97
  0

• Users should be able to debug single tests

  #18 opened 2 years ago by vaibhavsingh97
  0

• Users should be able to run multiple tests

  #19 opened 2 years ago by vaibhavsingh97
  0

• Users should be able to debug test at the cursor

  #21 opened 2 years ago by vaibhavsingh97
  0

• Users should be able to debug tests at the current opened tests file

  #22 opened 2 years ago by vaibhavsingh97
  0

• Creating Quick Pick Menu if User had chosen Install Nightwatch

  #4 opened 2 years ago by vaibhavsingh97
  0

• Passing Result of Quick Pick menu to Terminal, which install desired browser user had chosen, and add Nightwatch config in the root of the workspace project.

  #5 opened 2 years ago by vaibhavsingh97
  0

• Tagging each test with Unique ID (required By VS Code TestController) and making sure while parsing correct tree is formed with its children

  #7 opened 2 years ago by vaibhavsingh97
  0

• using --list-tests flags, implement test discovery in Visual Studio Code

  #6 opened 2 years ago by vaibhavsingh97
  1

• Make sure BDD interface tests should get displayed.

  #8 opened 2 years ago by vaibhavsingh97
  0

• Create/Parse tree in VS Code, and tag them with unique ID and other meta data for instance location, etc. In case of failure of tests, it helps in displaying error message in the editor

  #12 opened 2 years ago by vaibhavsingh97
  0

• Condition: Running all the tests

  #9 opened 2 years ago by vaibhavsingh97
  0

• Add option to debug tests

  #17 opened 2 years ago by vaibhavsingh97
  0

• Creating Install Nightwatch option in the command pallet

  #3 opened 2 years ago by vaibhavsingh97
  0

• Tests for Quick Pick Menu

  #26 opened 2 years ago by vaibhavsingh97
  0

• Setup Github Action

  #2 opened 2 years ago by vaibhavsingh97
  0

• Users should be able to rerun failed tests

  #23 opened 2 years ago by vaibhavsingh97
  0

• Making sure that User can navigate between different errors

  #15 opened 2 years ago by vaibhavsingh97
  0

• Initial Setup of the Extension Repository

  #1 opened 2 years ago by vaibhavsingh97
  1