Change main file tests to define sources inline

The tests are structured quite differently now but I think the new, smaller test cases cover all the interesting cases from the old test.

Author: ahoppen

Documentation/Development.md

@@ -40,7 +40,7 @@ $ swift build
 
 Install the following dependencies of SourceKit-LSP:
 
-* libsqlite3-dev libncurses5-dev python3 ninja-build
+* libsqlite3-dev libncurses5-dev python3
 
 ```sh
 $ export PATH="<path_to_swift_toolchain>/usr/bin:${PATH}"
@@ -134,81 +134,6 @@ Where "N" configures the log verbosity and is one of the following numbers: 0 (e
 
 As much as is practical, all code should be covered by tests. New tests can be added under the `Tests` directory and should use `XCTest`. The rest of this section will describe the additional tools available in the `SKTestSupport` module to make it easier to write good and efficient tests.
 
-### Test Projects (Fixtures)
-
-SourceKit test projects should be put in the `SKTestSupport/INPUTS` directory. Generally, they should use the [Tibs](#tibs) build system to define their sources and targets. An exception is for tests that need to specifically test the interaction with the Swift Package Manager. An example Tibs test project might look like:
-
-```
-SKTestSupport/
-  INPUTS/
-    MyTestProj/
-      a.swift
-      b.swift
-      c.cpp
-```
-
-Where `project.json` describes the project's targets, for example
-
-```
-{ "sources": ["a.swift", "b.swift", "c.cpp"] }
-```
-
-Tibs supports more advanced project configurations, such as multiple swift modules with dependencies, etc. For much more information about Tibs, including what features it supports and how it works, see [Tibs](#tibs).
-
-### SKTibsTestWorkspace
-
-The `SKTibsTestWorkspace` pulls together the various pieces needed for working with tests, including opening a connection to the language server, building the project to produce index data, loading source code into open documents, etc.
-
-To create a `SKTibsTestWorkspace`, use the `staticSourceKitTibsWorkspace` method (the intent is to provide a `mutableSourceKitTibsWorkspace` method in the future for tests that mutate source code).
-
-```swift
-func testFoo() {
-  // Create the workspace, including opening a connection to the TestServer.
-  guard let ws = try staticSourceKitTibsWorkspace(name: "MyTestProj") else { return }
-  let loc = ws.testLoc("myLocation")
-
-  // Build the project and populate the index.
-  try ws.buildAndIndex()
-
-  // Open a document from the test project sources.
-  try ws.openDocument(loc.url, language: .swift)
-
-  // Send requests to the server.
-  let response = try ws.sk.sendSync(...)
-}
-```
-
-#### Source Locations
-
-It is common to want to refer to specific locations in the source code of a test project. This is supported using inline comment syntax.
-
-```swift
-Test.swift:
-func /*myFuncDef*/myFunc() {
-  /*myFuncCall*/myFunc()
-}
-```
-
-In a test, these locations can be referenced by name. The named location is immediately after the comment.
-
-```swift
-
-let loc = ws.testLoc("myFuncDef")
-// TestLocation(url: ..., line: 1, column: 19)
-```
-
-`TestLocation`s can be easily converted to LSP `Location` and `Position`s.
-
-```swift
-Location(ws.testLoc("aaa:call"))
-Position(ws.testLoc("aaa:call"))
-```
-
 ### Long tests
 
 Tests that run longer than approx. 1 second are only executed if the the `SOURCEKIT_LSP_ENABLE_LONG_TESTS` environment variable is set to `YES` or `1`. This, in particular, includes the crash recovery tests.
-
-## Tibs
-
-We use Tibs, the "Test Index Build System" from the IndexStoreDB project to provide build system support for test projects, including getting compiler arguments and building an index. 
-For much more information about Tibs, see [IndexStoreDB/Documentation/Tibs.md](https://github.com/apple/indexstore-db/blob/main/Documentation/Tibs.md).