SampathKumarAmex opened a new pull request #690: URL: https://github.com/apache/jmeter/pull/690
## Description Split function unit test refactor with failure and different success scenarios. ## Motivation and Context 1. I have separated the test scenarios into three. - Failure scenario - Success scenario without passing any parameters - Success scenario with previous result value only Actually, it's good to further separate all the different variations in scenario #2. So that we will have feedback from all the tests in single execution (i.e. CI build) even when one of the test scenarios fail. Also, it improves the readability and help to understand the scenarios better. Having said that, I haven't done that as part of this PR. 2. Used the JUnit 5 assertions as the test is already using JUnit 5 `@Test` annotation. This is to make the JUnit 5 usage consistent in this test class ## How Has This Been Tested? n/a - Unit test refactoring ## Screenshots (if appropriate): ## Types of changes <!--- What types of changes does your code introduce? Delete as appropriate --> - Bug fix (non-breaking change which fixes an issue) ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [X] My code follows the [code style][style-guide] of this project. - [ ] I have updated the documentation accordingly. [style-guide]: https://wiki.apache.org/jmeter/CodeStyleGuidelines -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
