I want to give my users an option to select either local or remote backend. But it seems Terratest does not support setting path to the config file via -backend-config=PATH parameter, only key-value parameters.

AssertJ's AbstractIterableAssert is large. We don't have an equivalent to every last assertion (and this is sometimes intentional), but for cases in which we do have an equivalent, we could help prospective users / migrating users / users with

Describe the feature you'd like:

Being new to testing-library, it all is a bit overwhelming. The long list of matchers jest-dom introduces, also makes it harder to start out.

Suggested implementation:

Group the matchers in the documentation over some headings, e.g. “Checking element existence”, “Checking forms”, “Checking element state”.

Describe alternatives you've cons

https://docs.nose2.io/en/latest/configuration.html#configuration-files is missing a bit of crucial information: what is the name of the .ini file? It looks like it can be both "unittest.cfg" or "nose2.cfg" if I read the code. Is this correct?

Bandit needs a logo. The automatically generated avatar on GitHub always reminds me of that.

My initial idea was to combine the hexagon of the C++ logo, a bandit mask and a BDD cycle in one logo. The [result of my first attemp

So, I added this feature:

- await waitForElementToBeRemoved(() => screen.getByText('foo'))

+ const element = screen.getByText('foo')
+ await waitForElementToBeRemoved(element)

Both work, but the first I think is easier most of the time.

But I just learned that in React applications (and likely other frameworks) the DOM nodes aren't always removed, rather they're updated.

Currently, we are supporting Angular, React and Vue for shareable configurations. The configuration contains the following rules:

• await-async-query
• await-async-utils
• no-await-async-query
• no-debug
• no-dom-import

It would be nice to add shareable configurations for other libraries such as:

• Native Testing Library

By the next's document, this causes all pages to be executed on the server -- disabling Automatic Static Optimization.

I think react-navigation is the most popular navigation solution out there

so we should provide an easy way to just use the route config from react navigation

I have used testcafe-testing-library on chrome/firefox/IE11. Chrome and Firefox all work fine but I am having these errors on IE11:

An error occurred in Selector code: 
TypeError: Unable to get property 'apply' of undefined or null reference

An error occurred in a script injected into the tested page:
TypeError: Unable to get property 'for' of undefined or null reference

I am wonderin