tqcq/CPM.cmake
0
0
Fork 0
mirror of https://github.com/cpm-cmake/CPM.cmake.git synced 2025-11-19 16:57:56 -05:00
Code Issues Packages Projects Releases Wiki Activity

Feature/add missing packageproject options (#524)

Browse Source 
* Add missing packageproject options

* Fix typos with codespell

* Update test/style/CMakeLists.txt

Co-authored-by: Lars Melchior <TheLartians@users.noreply.github.com>

* fix-cmake-format

---------

Co-authored-by: Lars Melchior <TheLartians@users.noreply.github.com>
This commit is contained in:
Claus Klein
2024-01-17 09:06:16 +01:00
committed by GitHub
parent 369f1316f6
commit 3c25130ffa
8 changed files with 14 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
test/integration/README.md
View File

@@ -12,7 +12,7 @@ To run all tests from the repo root execute:
$ ruby test/integration/runner.rb
```
The runner will run all tests and generate a report of the exeuction.
The runner will run all tests and generate a report of the execution.
The current working directory doesn't matter. If you are in `<repo-root>/test/integration`, you can run simply `$ ruby runner.rb`.
@@ -34,7 +34,7 @@ Writing tests makes use of the custom integration test framework in `lib.rb`. It
* There should be no dependency between the test scripts. Each should be executable individually and the order in which multiple ones are executed mustn't matter.
* The class should contain methods, also prefixed with `test_` which will be executed by the framework. In most cases there would be a single test method per class.
* In case there are multiple test methods, they will be executed in the order in which they are defined.
* The test methods should contain assertions which check for the expected state of things at varous points of the test's execution.
* The test methods should contain assertions which check for the expected state of things at various points of the test's execution.
### More

2
test/integration/lib.rb
View File

@@ -143,7 +143,7 @@ class Project
end
class IntegrationTest < Test::Unit::TestCase
self.test_order = :defined # run tests in order of defintion (as opposed to alphabetical)
self.test_order = :defined # run tests in order of definition (as opposed to alphabetical)
def cleanup
# Clear cpm-related env vars which may have been set by the test

2
test/integration/tutorial.md
View File

@@ -14,7 +14,7 @@ class MyTest < IntegrationTest
end
```
Now we have our test case class, and the single test method that we will require. Let's focus on the method's contents. The integration test framework provides us with a helper class, `Project`, which can be used for this scenario. A project has an assoiciated pair of source and binary directories in the temporary directory and it provides methods to work with them.
Now we have our test case class, and the single test method that we will require. Let's focus on the method's contents. The integration test framework provides us with a helper class, `Project`, which can be used for this scenario. A project has an associated pair of source and binary directories in the temporary directory and it provides methods to work with them.
We start by creating the project: