Lines Matching +full:docs +full:- +full:lldb +full:- +full:html
10 http://docs.python.org/library/unittest.html for more details.
12 To just run the TestSettings.py test, chdir to the lldb test directory, and then
15 /Volumes/data/lldb/svn/trunk/test $ ./dotest.py settings
16 ----------------------------------------------------------------------
19 ----------------------------------------------------------------------
23 /Volumes/data/lldb/svn/trunk/test $
25 Pass '-v' option to the test driver to also output verbose descriptions of the
28 /Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v settings
29 ----------------------------------------------------------------------
33 Test that after 'set auto-confirm true', manual confirmation should not kick in. ... ok
35 Test that setting target.process.output-path for the launched process works. ... expected failure
39 Test that 'set term-width' actually changes the term-width. ... ok
41 Test that run-args and env-vars are passed to the launched process. ... ok
43 Test that run-args and env-vars are passed to the launched process. ... ok
45 ----------------------------------------------------------------------
49 /Volumes/data/lldb/svn/trunk/test $
51 Underneath, the '-v' option passes keyword argument verbosity=2 to the
53 http://docs.python.org/library/unittest.html#unittest.TextTestRunner). For very
54 detailed descriptions about what's going on during the test, pass '-t' to the
56 display their output. For brevity, the '-t' output is not included here.
59 of a bug currently in lldb such that setting target.process.output-path to
66 # settings set target.process.output-path does not seem to work
69 See http://docs.python.org/library/unittest.html for more details.
74 """Test that setting target.process.output-path for the launched process works."""
80 # Set the output-path and verify it is set.
81 self.runCmd("settings set target.process.output-path 'stdout.txt'")
82 self.expect("settings show target.process.output-path",
83 startstr = "target.process.output-path (string) = 'stdout.txt'")
89 "'stdout.txt' exists due to target.process.output-path.")
106 executable by lldb:
113 pass the specified command to the lldb command interpreter. It's like you're
114 typing the command within an interactive lldb session.
129 # Set the output-path and verify it is set.
131 self.runCmd("settings set target.process.output-path '%s'" %stdout)
132 self.expect("settings show target.process.output-path",
133 SETTING_MSG("target.process.output-path"),
134 startstr = "target.process.output-path (string) = '.*stdout.txt'")
137 target.process.output-path to be 'stdout.txt', instead of the default
145 startstr = "target.process.output-path (string) = '%s'" %stdout
162 "stdout.txt' exists due to target.process.output-path.")
192 system(["/bin/sh", "-c", "rm -f "+self.getBuildArtifact("output.txt")])
193 system(["/bin/sh", "-c", "rm -f "+self.getBuildArtifact("stdout.txt")])
197 with the particular test class. This is part of the so-called test fixture in
198 the unittest framework. From http://docs.python.org/library/unittest.html:
222 /Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v settings
223 ----------------------------------------------------------------------
227 Test that after 'set auto-confirm true', manual confirmation should not kick in. ... ok
229 Test that setting target.process.output-path for the launched process works. ... FAIL
233 Test that 'set term-width' actually changes the term-width. ... ok
235 Test that run-args and env-vars are passed to the launched process. ... ok
237 Test that run-args and env-vars are passed to the launched process. ... ok
241 Test that setting target.process.output-path for the launched process works.
242 ----------------------------------------------------------------------
244 …File "/Volumes/data/lldb/svn/trunk/test/settings/TestSettings.py", line 125, in test_set_output_pa…
245 "'stdout.txt' exists due to target.process.output-path.")
246 AssertionError: False is not True : 'stdout.txt' exists due to target.process.output-path.
248 ----------------------------------------------------------------------
252 /Volumes/data/lldb/svn/trunk/test $ ls 2010-10-19-14:10:49.059609
259 /Volumes/data/lldb/svn/trunk/test $
261 We get one failure and a timestamp directory 2010-10-19-14:10:49.059609.