You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the current tests make no longer sense from an UX perspective.
Example:
await t.waitForSelector('.neo-list-item.neo-navigator-active-item:contains("Wyoming")');
await t.type(null, '[ENTER]');
await t.waitForSelectorNotFound('.neo-picker-container:visible');
await t.waitFor(100);
t.is(inputField.value, 'Wyoming');
await t.type(null, '[DOWN]');
// Picker Must show with Wyoming activated
await t.waitForSelector('.neo-list-item.neo-navigator-active-item:contains("Wyoming")');
await t.type(null, '[UP]');
await t.waitForSelector('.neo-list-item.neo-navigator-active-item:contains("Wisconsin")');
input value changes will open the picker and filter the related list.
navigating to an item (Wyoming) and then hitting ENTER will drop this name into the input field and then the list gets filtered down to only contain this item. so, navigating up to an item which does not match the filter (Wisconsin) can not work.
Some of the current tests make no longer sense from an UX perspective.
Example:
input value changes will open the picker and filter the related list.
navigating to an item (Wyoming) and then hitting ENTER will drop this name into the input field and then the list gets filtered down to only contain this item. so, navigating up to an item which does not match the filter (Wisconsin) can not work.
@ExtAnimal
The text was updated successfully, but these errors were encountered: