[mdraza7544]

What & why

Fixes #42

When Selenium Boot fails during framework initialization, the user currently gets a generic error message without an easy way to see what actually caused the failure.

This makes configuration and environment problems harder to diagnose, especially when running tests through Maven or CI.

Changes

• Expose the underlying initialization exception before the suite is aborted.
• Keep the existing high-level Selenium Boot initialization error message.
• Make the original failure and its cause available in the test output.
• Keep the change focused on framework initialization error handling.

Type of change

• Bug fix
• New feature (opt-in, aligned with the framework philosophy)
• Documentation
• Internal refactor / test coverage

Checklist

• The change is limited to the initialization failure handling.
• The original exception is preserved.
• The existing initialization failure message is retained.
• No unrelated framework behavior was changed.

Notes for reviewers

The goal of this change is to make initialization failures easier to diagnose.

Previously, a bootstrap failure could surface only as:

Selenium Boot failed to initialize. Aborting test suite execution.

The underlying exception is now exposed so users can see the actual reason for the initialization failure and troubleshoot it without having to inspect the source code.

[shossain786]

Nice catch on #42 and a clean fix — this looks good. Merging it.