Abstract: A method for adjusting the resource allocation ratio between microservices used to run an application. A microservice test sequence is defined which has an order that follows the traffic flow through the microservices. Each microservice is analyzed in order of the test sequence to classify whether or not it is acting as a bottleneck for the application. This is done by measuring whether or not decrementing the microservice's resource causes the application throughput to decrease. For each microservice classified as a bottleneck and in reverse order of the test sequence, its resource is successively incremented until the application throughput starts to increase, indicating it is no longer acting as a bottleneck. The resource allocation ratio can then be adjusted to reflect this procedure.

Abstract: A method for adjusting the resource allocation ratio between microservices used to run an application. A microservice test sequence is defined which has an order that follows the traffic flow through the microservices. Each microservice is analyzed in order of the test sequence to classify whether or not it is acting as a bottleneck for the application. This is done by measuring whether or not decrementing the microservice's resource causes the application throughput to decrease. For each microservice classified as a bottleneck and in reverse order of the test sequence, its resource is successively incremented until the application throughput starts to increase, indicating it is no longer acting as a bottleneck. The resource allocation ratio can then be adjusted to reflect this procedure.

Abstract: An audio emitter configured to emit a sound creates a high-frequency copy of the sound to be emitted. The high-frequency copy of the sound is superimposed over the sound, resulting in a composite signal. The composite signal is emitted by the emitter. The high-frequency copy is at a frequency inaudible to humans, enabling a receiver to identify the emitter and/or the sound.

Abstract: A computer-implemented method for creating a higher order mutant for mutation testing software is disclosed. The method includes, for each software test of a set of software tests, identifying a respective code path. The method further includes, for each first order mutant of a plurality of first order mutants, associating the first order mutant with the one or more identified code paths it interacts with. The method further includes creating a higher order mutant by combining two or more first order mutants based on the one or more associated code paths.

Abstract: A computer-implemented method for creating a higher order mutant for mutation testing software is disclosed. The method includes, for each software test of a set of software tests, identifying a respective code path. The method further includes, for each first order mutant of a plurality of first order mutants, associating the first order mutant with the one or more identified code paths it interacts with. The method further includes creating a higher order mutant by combining two or more first order mutants based on the one or more associated code paths.