You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* moved integration tests to phpunit
* updated integration tests description in CONTRIBUTING.md
* added `name` parameter to `patchUser` so the sample file works properly
* added `Retrievable` interface to `VolumeType`
* added `HasWaiterTrait` to `Compute::Image`
* added `Token::validate()` function to check if Identity token is valid
---------
Co-authored-by: k0ka <k0ka@users.noreply.github.com>
|`-s``--service`| Allows you to refine tests by a particular service. A service corresponds to top-level directories in the `./integration` directory, meaning that `compute` and `identity` are services because they exist as sub-directories there. If omitted, all services are run.|Run compute service: `php ./tests/integration/run.php -s compute` Run all tests: `php ./tests/integration/run.php`|
250
-
|`-v``--version`| Allows you to refine by a particular service version. A version corresponds to the sub-directories inside a service directory, meaning that `v2` is a supported version of `compute` because it exists as a sub-directory inside the `compute` directory. If omitted, all versions are run.|Run v2 Compute tests: `php ./tests/integration/run.php -s compute -v v2` Run all compute tests: `php ./tests/integration/run.php -s compute`|
251
-
|`-t``--test`| Allows you to refine by a particular test. Tests are defined in classes like `integration\OpenStack\Compute\v2`. Each test method manually references a sample file. To refine which tests are run, list the name of the method in this class. If omitted, all tests are run.|Run create server test: `php ./tests/integration/run.php -s compute -v v2 -t createServer` Run all compute v2 tests: `php ./tests/integration/run.php -s compute -v v2`|
252
-
|`--debug`|||
253
-
| `--help` | A help screen is returned and no tests run | `php ./tests/integration/run.php --help`
254
-
255
-
256
262
## Style guide
257
263
258
264
We follow [PSR-2](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md) for our
@@ -281,14 +287,11 @@ required to adhere to:
281
287
282
288
### 1. Providing feedback
283
289
284
-
On of the easiest ways to get readily involved in our project is to let us know
290
+
One of the easiest ways to get readily involved in our project is to let us know
285
291
about your experiences using our SDK. Feedback like this is incredibly useful
286
292
to us, because it allows us to refine and change features based on what our
287
-
users want and expect of us. There are a bunch of ways to get in contact! You
288
-
can [ping us](https://developer.rackspace.com/support/) via e-mail, talk to us on irc
289
-
(#rackspace-dev on freenode), [tweet us](https://twitter.com/rackspace), or
290
-
submit an issue on our [bug tracker](/issues). Things you might like to tell us
291
-
are:
293
+
users want and expect of us. You can submit an issue on our [bug tracker](/issues).
294
+
Things you might like to tell us are:
292
295
293
296
* how easy was it to start using our SDK?
294
297
* did it meet your expectations? If not, why not?
@@ -309,8 +312,7 @@ breakthroughs on it so far.
309
312
We have three forms of documentation:
310
313
311
314
* short README documents that briefly introduce a topic
312
-
* reference documentation
313
-
* user documentation on http://docs.php-opencloud.com that includes
315
+
* user documentation on https://php-openstack-sdk.readthedocs.io that includes
314
316
getting started guides, installation guides and code samples
315
317
316
318
If you feel that a certain section could be improved - whether it's to clarify
0 commit comments