Releases: robotcodedev/robotcode
Releases · robotcodedev/robotcode
v0.9.6
added
- Variable analysis, finds undefined variables
- in variables, also inner variables like ${a+${b}}
- in inline python expression like ${{$a+$b}}
- in expression arguments of IF/WHILE statements like $a<$b
- in BuiltIn keywords which contains an expression or condition argument, like
Evaluate
,Should Be True
,Skip If
, ...
- Improve handling of completion for argument definitions
- Support for variable files
- there is a new setting
robotcode.robot.variableFiles
and correspondingvariableFiles
launch configuration setting - this corresponds to the
--variablefile
option from robot
- there is a new setting
v0.9.5
added
- Correct handling of argument definitions wich contains a default value from an allready defined argument
v0.9.4
- Correct handling of argument definitions wich contains a default value with existing variable with same name
- Implement "Uncaughted Failed Keywords" exception breakpoint
- from now this is the default breakpoint, means debugger stops only if a keyword failed and it is not called from:
- BuiltIn.Run Keyword And Expect Error
- BuiltIn.Run Keyword And Ignore Error
- BuiltIn.Run Keyword And Warn On Failure
- BuiltIn.Wait Until Keyword Succeeds
- BuiltIn.Run Keyword And Continue On Failure
- partially fixes #44
- speedup updating test exploers view
- from now this is the default breakpoint, means debugger stops only if a keyword failed and it is not called from:
v0.9.3
added
- Introduce setting
robotcode.robot.paths
and correspondend launch config propertypaths
- Specifies the paths where robot/robotcode should discover test suites. Corresponds to the 'paths' option of robot
- Introduce setting
robotcode.robot.variableFiles
and correspondend launch config propertyvariableFiles
- Specifies the variable files for robotframework. Corresponds to the '--variablefile' option of robot.
- Rework debugger termination
- if you want to stop the current run
- first click on stop tries to break the run like if you press CTRL+c to give the chance that logs and reports are written
- second click stops/kill execution
- if you want to stop the current run
- 'None' values are now shown correctly in debugger
v0.8.0
added
- Introduce new version scheme to support pre-release versions of the extension
- see README
- Rework handling VSCode test items to ensure all defined tests can be executed, also when they are ambiguous
- see #37
- Semantic highlighting of new WHILE and EXCEPT options for RF 5.0
- Support for inline IF for RF 5.0
- Support for new BREAK, CONTINUE, RETURN statements for RF 5.0
v0.7.9
- none so far
v0.7.5
0.7.5
v0.7.4
added
- automate uploading of release assets
v0.7.3
- automate creating github release for a new version tag
v0.7.0
added
- Add
dryRun
property to launch configuration - Add "Dry Run" and "Dry Debug" profile to test explorer
- You can select it via Run/Debug dropdown or Right Click on the "green arrow" before the test case/suite or in test explorer and then "Execute Using Profile"
- Mark using reserved keywords like "Break", "While",... as errors
- Support for NONE in Setup/Teardowns
- Decrease size of extension package
- Sligtly correct displayName and description of VSCode package, for better relevance in Marketplace search
- See here #39