WPLoader module table prefix sticks across suites, first applies about wp-browser HOT 1 CLOSED

While I understand how this could come in handy I've meddled into the code for a while: due to WordPress reliance on constants using the WPLoader module in two or more suites with different configurations will always prove an hazard. Now it's teh table prefix but it could be the database name, the multisite settings and so on.
One of my priorities is to avoid deviating, in the case of WPLoader, from the Core automated testing suite code so much to have to seriously fork it and getting around the "constant"s (pun intended) limit would require it.
I'm keeping this isssue open for memory and someday but labeling it as "wont-fix" for the time being as running the suites one by one is the recommended way to do it.
Adding a note in the README for this.

from wp-browser.