Clone Tools
  • last updated a few minutes ago
Constraints: committers
Constraints: files
Constraints: dates
remove reset from tests, not needed anymore

[AESH-231][AESH-232] moved some of the multiline code from Console to AeshInputProcessor cleanups in AeshInputProcessor enabled multiline test

    • -30
    • +19
[AESH-231] [AESH-232] Multi line input and completion doesn't work

fix test that might fail on environments that have non standard khome mapping

[AESH-230] checkstyle fix

[AESH-230] try to make Config.isPosixCompatible() smarter to detect if we're running under cygwin PosixTerminal must also use different stty options

dev cycle 0.54

releasing 0.53

Merge pull request #55 from koentsje/AESH-229

AESH-229: Drawing line should happen before moving cursor

AESH-229: Drawing line should happen before moving cursor

Merge pull request #54 from rbalent/AESH-226

AESH-226 - auto-complete not adding slash after full name of directory

AESH-226 - auto-comlete not adding slash after full name of directory

changed testcommand to show how username/password input could be implemented

show how to "hide" input

dev cycle 0.53

ready to release 0.52

[AESH-225] completion should work as expected when the completions size is over the set threshold.

[AESH-222] should also define the validatorinvocation value types for the validatorinvocationprovider

[AESH-222] validators should be able to get the command and context object while validating

[AESH-222] populate command when option name is not set

should populate before listing possible option names

make sure that the command object is populated when doing completion

0.52 dev cycle

0.51 release

console and exportmanager might be null

fixed vitests ignoring redirection and multiline tests for now...

    • -144
    • +370
Merge pull request #53 from aslakknutsen/test_failure

Add CountDownLatch and Exceptions List to feed information back to main ...

Update Console tests to use BaseConsoleTest.invokeTestConsole

invokeTestConsole handles:

* Creation of Pipes

* Creation of Console

* CountDownLatch setup

* Verification Exceptions

invokeTestConsole comes in 3 different varieties:

* Setup, Verify

* CallbackCount, Setup, Verify

* CallbackCount, Setup, Verify, SettingsBuilder

CallbackCount is the CoundDownLatch number to use. How many callbacks

should we wait for before moving on.

Add CountDownLatch and Exceptions List to feed information back to main thread

TestConsoleCallback function as a base class for ConsoleCallback in tests

that takes a CountDownLatch and List<Throwable>.

The TestConsoleCallback expose a verify method that can be used as a

replacement for execute in ConsoleCallback to verify the execution.

The TestConsoleCallback takes care of adding caught exceptions to the

exception list and call the CountDownLatch when done.

Waiting for the CoundDownLatch and re throw of Exceptions caught in the

TestConsoleCallback needs to be done in the Main thread executing the test

method so the errors are reported back to JUnit.

Remove travis ci gradle parallel override

Test failure has nothing to do with running in parallel