Here is the flow of the test: 1. Load the profiler 2. Load the JVM library 3. Start the JVM 4. Start the profiler 5. Execute the JVM task 6. Stop the profiler 7. Stop the JVM Expected output: The profiler should be able to profile the JVM task. Explanation: The JVM is loaded and started before the profiling session, so profiler correctly detects the JVM when the profiling session starts. */
| 213 | so profiler correctly detects the JVM when the profiling session starts. |
| 214 | */ |
| 215 | void testFlow1(int argc, char** argv) { |
| 216 | loadProfiler(); |
| 217 | |
| 218 | loadJvmLib(); |
| 219 | |
| 220 | startJvm(); |
| 221 | |
| 222 | startProfiler(); |
| 223 | |
| 224 | executeJvmTask(); |
| 225 | |
| 226 | stopProfiler(argv[2]); |
| 227 | |
| 228 | stopJvm(); |
| 229 | } |
| 230 | |
| 231 | /* |
| 232 | Here is the flow of the test: |
no test coverage detected