Great job! This will helps us to finally do CLI testing of the real application. Now I am working on the mock web support. I will have this ready this week too. Just in time for my training class.

I think that onRequest() and onClassRequest could be detected if we are actually running a direct template or class via the CLI.

I have all the life cycle methods working right now but onRequest and onClassRequest since I’m not sure exactly how well the fit in given their ability to intercept execution and the fact there are some assumptions made by them that don’t quite fit with our CLI execution. We can revisit those.

The logic to detect and invoke the application files is actually already in place. I was incorrect the other day when I said it wasn’t. Application and session lifecycle methods are already getting called as well. The only thing missing is we aren’t firing is any of request lifecycle listener methods like onRequest(), and onRequestStart() etc. So I think we just need to decide which ones we want to fire and wire that up. We also aren’t firing the onError() either. We just need to add that logic in.