beta-test-rf-live findings

Enhancements

• Implement code-completion for .py files
• Implement code-completion for variable names
• Implement code-completion for 'Library' keyword, e.g. when loading an additional Standard Library (e.g. OperatingSystem shall show up when typing Op)
• Show user that page/editor is still loading (e.g. after a new example has been selected)
• first time loading time ... could be improved
• Provide optional requirements.txt (as tab) file which can be loaded via micropip before execution?
• Allow Testing of WebPages, e.g. via Browser (I know, you're already working in it, right?)

Bugs

• Linking from report.html to log.html does not work
• "Run Tests" and "Run Test Suite" are duplicated when switching between tabs "EDITOR", "INSTALL", "LEARN"
• Padding to bottom with the log... not good.
• Close button for log disappears when changing the Log level
• Fonts for tabnames and ConsoleOutput header could be improved
• Second Test Run is finished before scrolling
• Code Lens Buttons (Run Test, Run Test Suite) cannot be clicked on mobile phone
• Once the Editor fills the full screen on your mobile phone, scrolling from Editor back to the top (to select different example) is tricky
• Font color of Description & Log is sometimes black on dark grey background
  • on Windows with MS Edge and Windows Dark Theme
  • on Mobile Phone with Chrome
• Clicking Code Lense buttton "Run Suite" in an example with multiple test suites (e.g. Variables) runs all existing .robot test suites (instead of only the current one)

Unclear

• When copying a link from the log.html (Link to this test) there is this weird and long URL.
  Is whole html is encoded in there?
• "Share" Button is only visible after modifications
• Strange side-effects when doing things like Remove Directory, Errors in Console Output and no scrolling, See Here
• Remove original description for a modified/shared example? See here

Les problèmes encore en suspens concernent l’éditeur, report.html, log.html, les fichiers .py, requirements.txt et les contrôles Run Test/Run Suite. Commencez par sélectionner un élément non coché et le reproduire dans l’aperçu lié, puis suivez le point d’entrée de la page ou de l’éditeur concerné. La tâche est terminée lorsque le comportement sélectionné est corrigé et vérifié, sans régression des éléments cochés.