076166c22f
Debugger: Generate line numbers for class initializers with a number on the 'init' keyword (KT-16277)
...
Debugger tests not absent as they use the bootstrap version of kotlinc.
Obviously, this change is not present in it yet.
2019-11-25 17:26:31 +09:00
ab0f841642
Debugger: Provide fixed implementation of 'toString()' for lambdas (KT-32691)
2019-11-25 17:26:27 +09:00
82a1750d26
Debugger: Forbid 'Nothing' constructor calls in evaluated code (KT-33093)
2019-11-25 17:26:27 +09:00
7bdda22cfa
[coroutine][debugger] broken testCompileOnly fix missing dependency aether-dependency-resolver in 192,193 versions
2019-11-22 07:27:18 +01:00
25acb1e191
[coroutine][debugger] removed and regenerated tests for not-ready-to-be-tested logic, kt* tests are failing due to KT-32691
2019-11-20 13:17:56 +03:00
1dc44b4000
Debugger: Tests refactor
2019-11-19 12:29:53 +03:00
4281fd6bd5
Don't write nop for extension lambda during inline
2019-11-14 08:17:33 +01:00
1309c0c67a
An attempt to fix flaky debugger tests
2019-10-24 21:33:01 +09:00
bf027fb824
Do not show Smart Step Into targets for @InlineOnly callables (KT-33728)
2019-10-24 21:33:00 +09:00
87e0a2d98c
Debugger: Fix evaluation of function declarations with expression bodies (KT-32704)
...
Before this commit, the substituted FunctionDescriptor didn't have a source element.
As a result, 'CodeFragmentParameterAnalyzer.isCodeFragmentDeclaration' failed to recognize such a descriptor as fragment-local, and it was erroneously captured.
2019-10-24 21:33:00 +09:00
716c9f79f7
Debugger: Do not use expression code fragments for evaluator (KT-32736, KT-32741)
...
It seems like it doesn't make much sense to create expression code fragments.
People type statements or several expressions separated with a semicolon to a single-line expression line.
That is exactly what block code fragment was designed for.
2019-10-24 21:33:00 +09:00
39662c09e9
Debugger: Fix breakpoints and stepping on a first line (KT-33304)
...
This commit fixes the 'SmartStepIntoTestGenerated#testFunWithExpressionBody' test.
2019-10-24 21:32:59 +09:00
9cc7ff0efc
Debugger: Fix "smart step into" for library declarations (KT-33303)
2019-10-24 21:32:59 +09:00
c6a5733b3d
Debugger: Move 'smart step into' classes to the 'smartStepInto' package
2019-10-24 21:32:59 +09:00
d2b058c1e5
Debugger: Extract Smart step visitor
2019-10-24 21:32:58 +09:00
8325216d38
Debugger: Fix "Step over" with inline function calls in non-functions (KT-20342)
2019-10-24 21:32:58 +09:00
4ed64b0283
Regenerate tests with TargetBackend.ANY remove and using runTest with this
2019-10-23 12:49:48 +03:00
3891f9fcaa
Refactoring: extract tests files utilities to separate class
2019-10-23 12:49:47 +03:00
9665870118
Fix AbstractSmartStepIntoTest tests in 193
2019-10-21 15:52:33 +03:00
93c91862f1
Fix debugger tests compilation in 193 after the big refactoring
2019-10-11 14:06:47 +03:00
55548d9199
Use test path relative to testDataPath in fixture.configureByFile to be complaint with 193, part 3
2019-10-09 07:34:25 +02:00
472ec72eb9
Refactor debugger tests
...
1. Move tests to their own module
2. Avoid sharing the 'tinyApp' project between tests
3. Clean up option directive handling
2019-10-08 19:13:56 +09:00
d8d81c51d7
Move debugger test data to the new location
2019-10-08 19:13:55 +09:00
Yan Zhulanow