Object result = jobExecutor.execute("javascript", "console.log('test')");
        assertEquals("Executed: javascript console.log('test')", result);

        result = jobExecutor.execute("python", "print('test')");
        assertEquals("Executed: python print('test')", result);

        result = jobExecutor.execute("groovy", "println 'test'");
        assertEquals("Executed: groovy println 'test'", result);
    }

 * that every {@code Runnable} that is {@linkplain #add added} will be executed after {@link
 * #execute()} is called. Any {@code Runnable} added after the call to {@code execute} is still
 * guaranteed to execute. There is no guarantee, however, that listeners will be executed in the
 * order that they are added.
 *

# Lifespan Events { #lifespan-events }

You can define logic (code) that should be executed before the application **starts up**. This means that this code will be executed **once**, **before** the application **starts receiving requests**.

The same way, you can define logic (code) that should be executed when the application is **shutting down**. In this case, this code will be executed **once**, **after** having handled possibly **many requests**.

These dependencies will be executed/solved the same way as normal dependencies. But their value (if they return any) won't be passed to your *path operation function*.

/// tip

Some editors check for unused function parameters, and show them as errors.

Using these `dependencies` in the *path operation decorator* you can make sure they are executed while avoiding editor/tooling errors.

                    logger.debug("Process {} is already executed.", p);
                }
            }
        }

        /**
         * Checks if the destroyer has been executed.
         * @return True if executed, false otherwise.
         */
        public boolean isExecuted() {
            return executed.get();
        }
    }

    /**

Using `Depends(scope="function")`, the exit code after `yield` is executed right after the *path operation function* is finished, before the response is sent back to the client.

And when using `Depends(scope="request")` (the default), the exit code after `yield` is executed after the response is sent.

{* ../../docs_src/debugging/tutorial001_py310.py hl[1,15] *}

### About `__name__ == "__main__"` { #about-name-main }

The main purpose of the `__name__ == "__main__"` is to have some code that is executed when your file is called with:

<div class="termy">

```console
$ python myapp.py
```

</div>

but is not called when another file imports it, like in:

```Python
from myapp import app
```

    @Resource
    private ScheduledJobService scheduledJobService;

    @Resource
    private SystemHelper systemHelper;

    @Resource
    private JobHelper jobHelper;

    /** The job class to be executed by this scheduler */
    protected Class<? extends LaJob> jobClass = ScriptExecutorJob.class;

    /** The timestamp when the scheduler was last updated */
    protected long schedulerTime;

    @Override

        String result = scoreUpdater.execute();

        // All boosters should be executed
        assertTrue(result.contains("TestScoreBooster : 100"));
        assertTrue(result.contains("TestScoreBooster : 200"));
        assertTrue(result.contains("TestScoreBooster : 300"));
    }

    // Test execute result format
    @Test
    public void test_execute_resultFormat() {

Only the code prior to and including the `yield` statement is executed before creating a response:

{* ../../docs_src/dependencies/tutorial007_py310.py hl[2:4] *}

The yielded value is what is injected into *path operations* and other dependencies:

{* ../../docs_src/dependencies/tutorial007_py310.py hl[4] *}

The code following the `yield` statement is executed after the response: