Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Differentiate between time spent on Spring related actions and the rest #15

Open
florianluediger opened this issue Mar 27, 2018 · 3 comments
Labels
enhancement New feature or request future Something that can be worked on later and shall be discussed then help wanted Extra attention is needed

Comments

@florianluediger
Copy link
Member

Currently the time spent on Spring related actions is calculated as follows:

Spring time = total time - test time

This way, all the time spent on other things that are not necessarily Spring related is included in this time.

@silasmahler silasmahler mentioned this issue Mar 27, 2018
3 tasks
@florianluediger florianluediger added the enhancement New feature or request label Mar 27, 2018
@silasmahler silasmahler added the future Something that can be worked on later and shall be discussed then label Mar 28, 2018
@silasmahler silasmahler added this to the Release 1.0.0 milestone Apr 2, 2018
@silasmahler silasmahler added the help wanted Extra attention is needed label Apr 4, 2018
@silasmahler silasmahler modified the milestones: Release 1.0.0, Release 1.1.0 Apr 4, 2018
@silasmahler
Copy link
Member

We need to investigate if there are more lifecyclehooks or options to determine the time.
Maybe we can ask someone from the JUnit5-Team in this regard.

@florianluediger
Copy link
Member Author

When starting a spring context with Spring Boot, there is a log output saying "XyContext: initialization completed in 4711 ms"
If we find this in the spring boot code, we might be able to extract this information the same way that Spring Boot does.

@florianluediger
Copy link
Member Author

Spring boot is not actually responsible for this log output, because it comes from the ContextLoader from the core spring framework and there does not seem to be a way to extract that information in the same way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request future Something that can be worked on later and shall be discussed then help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants