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);
    }

# 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.

    }

    eventListener.canceled(this)
  }

  override fun isCanceled(): Boolean = canceled

  override fun execute(): Response {
    check(executed.compareAndSet(false, true)) { "Already Executed" }

    timeout.enter()
    callStart()
    try {
      client.dispatcher.executed(this)
      return getResponseWithInterceptorChain()
    } finally {
      client.dispatcher.finished(this)
    }
  }

		l.Logger.ErrorContext(ctx, "SQL executed", slog.Attr{
			Key:   "trace",
			Value: slog.GroupValue(fields...),
		})

	case l.SlowThreshold != 0 && elapsed > l.SlowThreshold:
		l.Logger.WarnContext(ctx, "SQL executed", slog.Attr{
			Key:   "trace",
			Value: slog.GroupValue(fields...),
		})

	case l.LogLevel >= Info:
		l.Logger.InfoContext(ctx, "SQL executed", slog.Attr{
			Key:   "trace",

        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
    public void test_execute_resultFormat() {

    // the underlying supplier hasn't executed yet
    assertEquals(0, countingSupplier.calls);

    assertEquals(10, (int) memoizedSupplier.get());

    // now it has
    assertEquals(1, countingSupplier.calls);

    assertEquals(10, (int) memoizedSupplier.get());

    // it still should only have executed once due to memoization
    assertEquals(1, countingSupplier.calls);
  }

{* ../../docs_src/debugging/tutorial001.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
```

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

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

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

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

The code following the `yield` statement is executed after creating the response but before sending it:

            // but we mainly want to ensure the method signature is correct
            testTarget.expired();

            // If we get here, the method executed successfully
            assertTrue("expired method executed successfully", true);
        } catch (Throwable t) {
            // In test environments, system monitoring may fail due to missing dependencies