Kumar Chandresh

The comment button doesn't get enabled when used from toolbar

1

Since GitHub comment button gets enabled when there is content in the `textarea` input block. But if the only thing in the input is an emoji inserted using the toolbar,...

Some font characters are not rendered completely.

2

Since I don't know much about the font rendering, I thought I'll just put a screenshot of the problem.  In the above image why the `@` symbol is getting...

Nightwatch holds onto report writing until the end of execution of all tests which results in high memory consumption

1

### Description Our codebase has different groups (folders) of tests, viz. 1. `./tests/CRUD` 1. `./tests/UI` 1. `./tests/Happy-Path` 1. `./tests/E2E` Now these groups (folders) contain a lot of suites (files) that...

beforeEach does not run if test doesn't contain any lifecycle hooks

4

### Description of the bug/issue When I _write a command in `beforeEach` hook in `globals.js` and don't write any `before` or `after` hooks in the test suite_, I expected _that...

`this.api` is `undefined` in page-object when pattern `page.CustomCommand().pageCommand()` is wrapped inside the `perform()` command

2

### Description of the bug/issue When I chain a page-command with a custom-command inside a `browser.perform()` command, `this.api` becomes `undefined` in the page object. The following passes ✅ ```js pageObj.CustomCommand().pageCommand();...

Section commands ignore 'use_xpath: true' locateStrategy for simple string selectors.

2

### Description of the bug/issue When I use xpath selectors string in section commands, for example, `this.click('//div')`, and I have set `use_xpath: true` in nightwatch config, I expect the section...

Why not support CapsLock for key input source?

1

While we are at the topic, consider Scroll Lock and Num Lock as well. 😁

Since I am a beginner in Nightwatch.js and automation in general, Nightwatch documentation serves as a reliable source for understanding general concepts. The code snippet used as an example on...

[Bug] `$global` variable in `"uninstaller"` script is set to `$true` for user-level installation

2

## Bug Report #### Current Behavior The `$global` variable in `"uninstaller"` script is set to `$true` for user-level installations. #### Expected Behavior `$global` should be set to `$false` for user-level...