Class ThroughputControllerWrapper

    • Method Detail

      • maxThroughput

        protected java.lang.String maxThroughput()
      • percentThroughput

        protected java.lang.String percentThroughput()
      • getGuiClass

        public java.lang.Class<?> getGuiClass()
        Description copied from interface: JMeterGUIWrapper
        Gui Test Class used by Jmeter TestElement.GUI_CLASS @See TestElement
      • getTestClass

        public java.lang.Class<?> getTestClass()
        Description copied from interface: TestElementWrapper
        Test Class used by Jmeter TestElement.TEST_CLASS. @See TestElement.
      • getThroughput

        public java.lang.String getThroughput()
        A number. For percent execution mode, a number from 0-100 that indicates the percentage of times the controller will execute. "50" means the controller will execute during half the iterations through the test plan. For total execution mode, the number indicates the total number of times the controller will execute.
      • setThroughput

        public void setThroughput​(java.lang.String throughput)
        A number. For percent execution mode, a number from 0-100 that indicates the percentage of times the controller will execute. "50" means the controller will execute during half the iterations through the test plan. For total execution mode, the number indicates the total number of times the controller will execute.
      • isPerUser

        public boolean isPerUser()
        If checked, per user will cause the controller to calculate whether it should execute on a per user (per thread) basis. If unchecked, then the calculation will be global for all users. For example, if using total execution mode, and uncheck "per user", then the number given for throughput will be the total number of executions made. If "per user" is checked, then the total number of executions would be the number of users times the number given for throughput.
      • setPerUser

        public void setPerUser​(boolean perUser)
        If checked, per user will cause the controller to calculate whether it should execute on a per user (per thread) basis. If unchecked, then the calculation will be global for all users. For example, if using total execution mode, and uncheck "per user", then the number given for throughput will be the total number of executions made. If "per user" is checked, then the total number of executions would be the number of users times the number given for throughput.