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

v0.9.3

added

• Introduce setting robotcode.robot.paths and correspondend launch config property paths
  • 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 property variableFiles
  • 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
• '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
  • see here
  • fixes #38
• Decrease size of extension package
• Sligtly correct displayName and description of VSCode package, for better relevance in Marketplace search
  • See here #39

v0.6.0

added

• Improved variable analysis

  • In an expression like ${A+'${B+"${F}"}'+'${D}'} ${C}, every single 'inner' variable will be recognized, you can hover over it, it can be found as reference, you can go to the definition, ...
  • Also in python expressions like ${{$a+$b}} variables are recognized
  • Support for variables in expression in IF and WHILE statements
    • in something like $i<5 the variables are recognized
  • Only the name of the variable is used for hovering, goto and ..., not the surrounding ${}

• Support importing variable files as module for RobotFramework 5

• Depending on selected testcase names contains a colon, a semicolon is used as separator of prerunmodifier for executing testcases

  • fixes #20
  • note: i think you should not use colons or semicolon in testcase names ;-)

• Improve Debugger

  • The debugger shows variables as inline values and when hovering, it shows the current variable value not the evaluted expression
  • Variables in the debugger are now resolved correctly and are sorted into Local/Test/Suite and Global variables
  • Fix stepping/halt on breakpoint for IF/ELSE statements if the expression is evaluated as False
  • Rework of stepping and stacktrace in the debugger
    • Only the real steps are displayed in the stack trace

• Optimize keyword matching

  • all keyword references also with embedded arguments + regex are found
  • ambigous embedded keywords are recognized correctly, also with regex
  • speed up finding keyword references
  • fix #28
  • addresses #24

• Ignoring robotcode diagnostics

  • you can put a line comment to disable robotcode diagnostics (i.e errors or warnings) for a single line, like this:

  *** Test cases ***
  first
      unknown keyword  a param   # robotcode: ignore
      Run Keyword If    ${True}
      ...    Log    ${Invalid var        # robotcode: ignore
      ...  ELSE
      ...    Unknown keyword  No  # robotcode: ignore

• Propagate import errors from resources

  • errors like: Resource file with 'Test Cases' section is invalid are shown at import statement
  • Note: Robocop has it's own ignore mechanism

• Initialize logging only of "--log" parameter is set from commandline

  • fixes #30

• Optimize loading of imports and collecting keywords

  • this addresses #24
  • one of the big points here is, beware of namespace pollution ;-)

• Full Support for BDD Style keywords

  • includes hover, goto, highlight, references, ...