GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Calls to Kotlin autogenerated setter isn't changed to direct property access for tests from fuzzer · Issue #1241 · UnitTestBot/UTBotJava Closed Labels comp-codegenIssue is related to code generatorIssue is related to code generatorcomp-fuzzingIssue is related to the fuzzingIssue is related to the fuzzingctg-bugIssue is a bugIssue is a buglang-kotlinIssue is related to Kotlin language supportIssue is related to Kotlin language support DescriptionDescription Fixes from #1002 seems not to work properly if the model is produced by fuzzer. To Reproduce Launch action on the following class (use only fuzzer): class Example() { var x: Int = 3 fun f(): Int { return x } } Expected behavior Tests are generated properly. Actual behavior Incorrect tests with calls to Visual proofs (screenshots, logs, images) Example of generated test: @Test @DisplayName("f: arg_0 = Example() -> return 1409199696") fun testF() { val example = Example() example.setX(1409199696) val actual = example.f() assertEquals(1409199696, actual) } Environment Test generation method -- Fuzzing 100% Activity
MetadataMetadataAssigneesLabelscomp-codegenIssue is related to code generatorIssue is related to code generatorcomp-fuzzingIssue is related to the fuzzingIssue is related to the fuzzingctg-bugIssue is a bugIssue is a buglang-kotlinIssue is related to Kotlin language supportIssue is related to Kotlin language support TypeProjects
MilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402520 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |