TestingLifecycleHookKt

All Implemented Interfaces:


public final class TestingLifecycleHookKt

Nested Class Summary

Nested Classes
Modifier and Type	Class	Description

Field Summary

Fields
Modifier and Type	Field	Description
`private final static Boolean`	`isTemplate`
`private static TestingLifecycleHook`	`testingLifecycleHook`

Constructor Summary

Constructors
Constructor	Description

Enum Constant Summary

Enum Constants
Enum Constant	Description

Method Summary

Modifier and Type	Method	Description
`final Boolean`	`getIsTemplate()`
`TestingLifecycleHook`	`getTestingLifecycleHook()`	If you need to hook into the testing lifecycle (e.g.
`void`	`setTestingLifecycleHook(TestingLifecycleHook testingLifecycleHook)`	If you need to hook into the testing lifecycle (e.g.
`final static Unit`	`cleanupDialogs()`	Flow Server does not close the dialog when Dialog.close is called; instead it tells client-side dialog to close, which then fires event back to the server that the dialog was closed, and removes itself from the DOM.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
- Method Detail
  - getIsTemplate
```
 final Boolean getIsTemplate()
```
  - getTestingLifecycleHook
```
 TestingLifecycleHook getTestingLifecycleHook()
```
    If you need to hook into the testing lifecycle (e.g. you need to wait for any async operations to finish), set your custom implementation here. See TestingLifecycleHook for more info on where exactly you can hook into.
  - setTestingLifecycleHook
```
 void setTestingLifecycleHook(TestingLifecycleHook testingLifecycleHook)
```
    If you need to hook into the testing lifecycle (e.g. you need to wait for any async operations to finish), set your custom implementation here. See TestingLifecycleHook for more info on where exactly you can hook into.
  - cleanupDialogs
```
 final static Unit cleanupDialogs()
```
    Flow Server does not close the dialog when Dialog.close is called; instead it tells client-side dialog to close, which then fires event back to the server that the dialog was closed, and removes itself from the DOM. Since there's no browser with browserless testing, we need to cleanup closed dialogs manually, hence this method.