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.

Sign up for GitHub

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

Jump to bottom

DataProvider: possibility to unload dataprovider class, when done with it #2739

Merged
merged 1 commit into from Apr 21, 2022
Merged

DataProvider: possibility to unload dataprovider class, when done with it #2739

merged 1 commit into from Apr 21, 2022

Commits on Apr 21, 2022

  1. DataProvider: possibility to unload dataprovider class, when done wit… 

    …h it

With current Data providers implementation, it's code will stick around
in method area (JVM spec $2.5.4) for the entire test run.

By specifying dataprovider class with it's full qualified name, and
by using new custom classloader to load it, when needed, JVM gets a
chance to unload dataprovider class, when we're done with it.

Testing dataprovider class unload is performed by analysing memory dumps.
Also, there is a test(comparePerformanceAgainstCsvFiles) to measure performance
of data as code approach against common data approch, where data is stored in
csv files.
    Dzmitry Sankouski committed Apr 21, 2022
    Configuration menu
    Copy the full SHA
    c1c74b6 View commit details
    Browse the repository at this point in the history