summaryrefslogtreecommitdiffstats
path: root/lldb/test/lang/objc/objc-new-syntax/TestObjCNewSyntax.py
Commit message (Collapse)AuthorAgeFilesLines
* Move lldb/test to lldb/packages/Python/lldbsuite/test.Zachary Turner2015-10-281-103/+0
| | | | | | | | | | | This is the conclusion of an effort to get LLDB's Python code structured into a bona-fide Python package. This has a number of benefits, but most notably the ability to more easily share Python code between different but related pieces of LLDB's Python infrastructure (for example, `scripts` can now share code with `test`). llvm-svn: 251532
* Rename `lldb_shared` to `use_lldb_suite`.Zachary Turner2015-10-271-1/+1
| | | | llvm-svn: 251444
* Add from __future__ import print_function everywhere.Zachary Turner2015-10-231-0/+2
| | | | | | | | | | | | | Apparently there were tons of instances I missed last time, I guess I accidentally ran 2to3 non-recursively. This should be every occurrence of a print statement fixed to use a print function as well as from __future__ import print_function being added to every file. After this patch print statements will stop working everywhere in the test suite, and the print function should be used instead. llvm-svn: 251121
* Update every test to import `lldb_shared`.Zachary Turner2015-10-221-7/+3
| | | | | | | | | | | | | | | | | | | | | This is necessary in order to allow third party modules to be located under lldb/third_party rather than under the test folder directly. Since we're already touching every test file anyway, we also go ahead and delete the unittest2 import and main block wherever possible. The ability to run a test as a standalone file has already been broken for some time, and if we decide we want this back, we should use unittest instead of unittest2. A few places could not have the import of unittest2 removed,because they depend on the unittest2.expectedFailure or skip decorators. Removing all those was orthogonal in spirit to the purpose of this CL, so the import of unittest2 remains in those files that were using it for its test decorators. Those can be addressed separately. llvm-svn: 251055
* Merge dwarf and dsym testsTamas Berghammer2015-09-301-34/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently most of the test files have a separate dwarf and a separate dsym test with almost identical content (only the build step is different). With adding dwo symbol file handling to the test suit it would increase this to a 3-way duplication. The purpose of this change is to eliminate this redundancy with generating 2 test case (one dwarf and one dsym) for each test function specified (dwo handling will be added at a later commit). Main design goals: * There should be no boilerplate code in each test file to support the multiple debug info in most of the tests (custom scenarios are acceptable in special cases) so adding a new test case is easier and we can't miss one of the debug info type. * In case of a test failure, the debug symbols used during the test run have to be cleanly visible from the output of dotest.py to make debugging easier both from build bot logs and from local test runs * Each test case should have a unique, fully qualified name so we can run exactly 1 test with "-f <test-case>.<test-function>" syntax * Test output should be grouped based on test files the same way as it happens now (displaying dwarf/dsym results separately isn't preferable) Proposed solution (main logic in lldbtest.py, rest of them are test cases fixed up for the new style): * Have only 1 test fuction in the test files what will run for all debug info separately and this test function should call just "self.build(...)" to build an inferior with the right debug info * When a class is created by python (the class object, not the class instance), we will generate a new test method for each debug info format in the test class with the name "<test-function>_<debug-info>" and remove the original test method. This way unittest2 see multiple test methods (1 for each debug info, pretty much as of now) and will handle the test selection and the failure reporting correctly (the debug info will be visible from the end of the test name) * Add new annotation @no_debug_info_test to disable the generation of multiple tests for each debug info format when the test don't have an inferior Differential revision: http://reviews.llvm.org/D13028 llvm-svn: 248883
* OS X unexpected success cleanupTodd Fiala2015-09-141-2/+4
| | | | | | | | | | TestPersistObjCPointeeType and TestObjCNewSyntax marked up to expect success on clang >= 7.0.0. TestMultipleDebuggers passed 25/25 times, taking off intermittent. If this changes, I'll make sure it goes into a flaky/flakey category. llvm-svn: 247601
* Skip the rest of the Objective C tests on Windows.Zachary Turner2015-09-021-0/+1
| | | | llvm-svn: 246726
* Reversed r238363, because the message is inconsistentSean Callanan2015-07-011-1/+1
| | | | | | with all the other assertion messages. llvm-svn: 241212
* [TestBase.runCmd] Better error message when runCmd fails.Siva Chandra2015-05-271-1/+1
| | | | | | | | | | | | | | | | | | | | | Summary: Before: AssertionError: False is not True : Process is launched successfully After: AssertionError: False is not True : Command 'run a.out' failed. >>> error: invalid target, create a target using the 'target create' command >>> Process could not be launched successfully Reviewers: clayborg Reviewed By: clayborg Subscribers: lldb-commits, vharron Differential Revision: http://reviews.llvm.org/D9948 llvm-svn: 238363
* Working on getting the OSX build greenVince Harron2015-05-121-0/+2
| | | | | | | | | | | | | | Added missing SBLanguageRuntime.h to lldb.xcodeproj, set to Public (fixed compile error in TestPublicAPIHeaders) Removed reference to (temporarily) missing gtest.xcodeproj Fixed TestDeadStrip compile error XFAIL TestPublicAPIHeaders - test passes but teardown command 'settings remove target.env-vars DYLD_LIBRARY_PATH' fails XFAIL TestCModules - use of undeclared identifier 'MIN' XFAIL TestModulesAutoImport - clang: error: unknown argument: '-gmodules' XFAIL TestObjCNewSyntax - expr -- @((char*)"Hello world" + 6) cannot box a string value because NSString has not been declared http://reviews.llvm.org/D9643 llvm-svn: 237085
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-301-1/+1
| | | | | | | | | | | | | | | | against remote platform. Adds @skipIfPlatform and @skipUnlessPlatform decorators which will skip if / unless the target platform is in the provided platform list. Test Plan: ninja check-lldb shows no regressions. When running cross platform, tests which cannot run on the target platform are skipped. Differential Revision: http://reviews.llvm.org/D8665 llvm-svn: 233547
* Skip ObjC test on FreeBSD that does not buildEd Maste2014-10-271-0/+1
| | | | llvm-svn: 220681
* Skip dsym test on !DarwinEd Maste2014-10-201-0/+1
| | | | | | | | | | | r219978 fixed this test to work on Darwin, and removed the expected failure decorator, but it then started running (and failing) on FreeBSD. I'd think @dsym_test should skip the test on all non-Darwin operating systems. It seems not to be the case, so for now skip it the same way as done for other @dsym_test tests. llvm-svn: 220219
* Fix this test case to actually work - it was relying on a certain 'po' ↵Enrico Granata2014-10-161-14/+10
| | | | | | output which wasn't occurring llvm-svn: 219978
* Modified some test annotations so that tests on Linux that should be skipped ↵Todd Fiala2014-03-041-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | don't show up as XFAIL. The following two tests showed up as XFAIL even though they should always be skipped on Linux, due to the @unittest2.expectedFailure annotation appearing above the @dsym_test annotation: TestObjCNewSyntax.ObjCNewSyntaxTestCase.test_expr_with_dsym TestBlocks.BlocksTestCase.test_expr_with_dsym. For those two, I simply moved the @dsym_test annotation to the top so that it would be marked for skip ahead of being marked for XFAIL. TestObjCNewSyntax.ObjCNewSyntaxTestCase.test_expr_with_dwarf I marked as @skipIfLinux since my understanding is that isn't a valid test to run on Linux. So rather than categorize as a fail (i.e. something wrong to be fixed), just skip it. (My recent changes to Linux tests have been following that model: if it could never work, skip; if it's broken, mark XFAIL so we can easily track, fix, notice the fix and adjust accordingly). TestDeadStrip.DeadStripTestCase.test_with_dwarf I had previously marked as XFAIL but this would never work on Linux with the current linker AFAICT. Marked it as skip. llvm-svn: 202788
* Massive test suite cleanup to stop everyone from manually having to compute ↵Greg Clayton2013-12-101-1/+1
| | | | | | | | | | "mydir" inside each test case. This has led to many test suite failures because of copy and paste where new test cases were based off of other test cases and the "mydir" variable wasn't updated. Now you can call your superclasses "compute_mydir()" function with "__file__" as the sole argument and the relative path will be computed for you. llvm-svn: 196985
* Option changes:Enrico Granata2012-12-121-20/+20
| | | | | | | | | | | | | | | | | the option to print the runtime-specific description has been modified in the frame variable, memory read and expression command. All three commands now support a --object-description option, with a shortcut of -O (uppercase letter o) This is a breaking change: frame variable used --objc as the long option name expression used -o as a shortcut memory read uses --objd as the long option name Hopefully, most users won't be affected by the change since people tend to access "expression --object-description" under the alias "po" which still works The test suite has been tweaked accordingly. llvm-svn: 169961
* Fix all the test case breakages caused by folks writing tests all over the ↵Jim Ingham2012-09-221-2/+2
| | | | | | | | place that depended explicitly on the output of "break set". Please don't do this sort of thing!!!!! llvm-svn: 164433
* Mark the test as failing on both architectures, since LLDB won't handle the ↵Filipe Cabecinhas2012-05-301-2/+2
| | | | | | function to clang. llvm-svn: 157679
* Fixed the new-syntax testcase to reflect how weSean Callanan2012-05-211-1/+1
| | | | | | print string literals. llvm-svn: 157213
* I have updated Clang to include support for Objective-CSean Callanan2012-05-171-5/+9
| | | | | | | | | | boxed expressions returning numbers and strings. I also added boxed expressions to our testcases, and enabled boxed expressions when libarclite is linked into the inferior. llvm-svn: 157026
* Add i386-only expectedFailure decorators for current ToT.Johnny Chen2012-05-151-0/+2
| | | | llvm-svn: 156855
* Second batch of adding @dsym_test/@dwarf_test decorators to existing test cases.Johnny Chen2012-04-061-0/+2
| | | | | | | Plus some minor cleanup of test method names. Third and final batch is coming. llvm-svn: 154197
* Remove a debug statement.Johnny Chen2012-03-141-2/+0
| | | | llvm-svn: 152732
* Updated the revision of LLVM/Clang used by LLDB.Sean Callanan2012-03-081-0/+124
This takes two important changes: - Calling blocks is now supported. You need to cast their return values, but that works fine. - We now can correctly run JIT-compiled expressions that use floating-point numbers. Also, we have taken a fix that allows us to ignore access control in Objective-C as in C++. llvm-svn: 152286
OpenPOWER on IntegriCloud