mirror of
https://github.com/moodle/moodle.git
synced 2025-08-07 01:46:45 +02:00
b5c6ce0d7f
Before this patch the exported users (to csv file that jmeter consumes) were all the enrolled users in the test course. And that's ok when the number of users enrolled match the number of concurrent threads planned for a jmeter plan (each thread is a user). But when both numbers don't match, that can lead to the jmeter plan not behaving as expected, because it iterates over the excessive users in the file, leading to some users having run 5 loops, others 4... The only way to make results more consistent is to, always, ensure that the number of users exported for the plan match the plan size and not the site size. And that's what this issue exactly does, restrict the export to the number of threads that the plan will have. So every user always runs the very same number of loops.
13 lines
709 B
Text
13 lines
709 B
Text
This files describes API changes in core libraries and APIs,
|
|
information provided here is intended especially for developers.
|
|
|
|
=== 4.0 ===
|
|
|
|
* Function tool_generator_testplan_backend::create_users_file() now supports to pass the size of the testing plan,
|
|
that needs to be equal or smaller than the size of the generated site. That's used to effectively restrict the
|
|
exported number of users to the number of threads the jmeter plan will have (previously all the enrolled users
|
|
were being exported, with that leading to "false" loops (users not really looping X times).
|
|
|
|
=== 3.7 ===
|
|
|
|
* Function tool_generator_testplan_backend::get_course_options() is removed, the 'course' form element is used instead.
|