[lldb/test] Add test for the scripting template list command

[medismailben]

This patch adds a shell test to verify the output of the scripting template list command as discussed in #101672

[llvmbot]

@llvm/pr-subscribers-lldb

Author: Med Ismail Bennani (medismailben)

Changes

This patch adds a shell test to verify the output of the scripting template list command.

---

Full diff: https://github.com/llvm/llvm-project/pull/101726.diff

1 Files Affected:

• (added) lldb/test/Shell/Commands/command-scripting-template-list.test (+38)

diff --git a/lldb/test/Shell/Commands/command-scripting-template-list.test b/lldb/test/Shell/Commands/command-scripting-template-list.test
new file mode 100644
index 0000000000000..906f012618443
--- /dev/null
+++ b/lldb/test/Shell/Commands/command-scripting-template-list.test
@@ -0,0 +1,38 @@
+# REQUIRES: python
+# RUN: %lldb -s %s -o exit | FileCheck %s
+
+scripting template list
+# CHECK:Available scripted extension templates:
+# CHECK-NEXT:  Name: OperatingSystemPythonInterface
+# CHECK-NEXT:  Language: Python
+# CHECK-NEXT:  Description: Mock thread state
+# CHECK-NEXT:  API Usages: None
+# CHECK-NEXT:  Command Interpreter Usages:
+# CHECK-NEXT:    settings set target.process.python-os-plugin-path <script-path>
+# CHECK-NEXT:    settings set process.experimental.os-plugin-reports-all-threads [0/1]
+# CHECK-NEXT:  Name: ScriptedPlatformPythonInterface
+# CHECK-NEXT:  Language: Python
+# CHECK-NEXT:  Description: Mock platform and interact with its processes.
+# CHECK-NEXT:  API Usages: None
+# CHECK-NEXT:  Command Interpreter Usages: None
+# CHECK-NEXT:  Name: ScriptedProcessPythonInterface
+# CHECK-NEXT:  Language: Python
+# CHECK-NEXT:  Description: Mock process state
+# CHECK-NEXT:  API Usages:
+# CHECK-NEXT:    SBAttachInfo.SetScriptedProcessClassName
+# CHECK-NEXT:    SBAttachInfo.SetScriptedProcessDictionary
+# CHECK-NEXT:    SBTarget.Attach
+# CHECK-NEXT:    SBLaunchInfo.SetScriptedProcessClassName
+# CHECK-NEXT:    SBLaunchInfo.SetScriptedProcessDictionary
+# CHECK-NEXT:    SBTarget.Launch
+# CHECK-NEXT:  Command Interpreter Usages:
+# CHECK-NEXT:    process attach -C <script-name> [-k key -v value ...]
+# CHECK-NEXT:    process launch -C <script-name> [-k key -v value ...]
+# CHECK-NEXT:  Name: ScriptedThreadPlanPythonInterface
+# CHECK-NEXT:  Language: Python
+# CHECK-NEXT:  Description: Alter thread stepping logic and stop reason
+# CHECK-NEXT:  API Usages: SBThread.StepUsingScriptedThreadPlan
+# CHECK-NEXT:  Command Interpreter Usages: thread step-scripted -C <script-name> [-k key -v value ...]
+
+scripting template list -l lua
+# CHECK: Available scripted extension templates: None

[JDevlieghere]

Do you get the same output regardless of whether you're building with or without lua support? If so then this is fine, otherwise this would have to go into a separate test that contains REQUIRES: lua.

[medismailben]

Yeah, I tested locally without Lua support.