Skip to content

Commit 5bd797f

Browse files
authored
Merge pull request #103 from thefrontside/mk/readme
Apply consistent format for all READMEs
2 parents bce993c + 86603ee commit 5bd797f

File tree

4 files changed

+17
-41
lines changed

4 files changed

+17
-41
lines changed

README.md

Lines changed: 13 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -5,35 +5,17 @@
55

66
# Simulacrum
77

8-
A simulation platform to supercharge acceptance testing, enable
9-
high-fidelity application previews, and free up development teams to
10-
make progress independently.
11-
12-
Modern applications have modern dependencies. Whether they run on the
13-
server or in the browser, they rely on external services to get their
14-
jobs done. But along with the power to focus our business logic and
15-
distribute it across so many different points comes a fundamental
16-
weakness: The entire experience, from development, to testing, to
17-
continuous integration is coupled to the very in-the-moment states of
18-
actual deployments. This becomes problematic when those deployments
19-
are down, rate limited, under active development, or not functioning
20-
as expected in any way.
21-
22-
Simulacrum removes these constraints from your process by allowing you
23-
to simulate external dependencies with a very high degree of
24-
reality.
8+
A simulation platform to supercharge acceptance testing, enable high-fidelity application previews, and free up development teams to make progress independently.
259

26-
## Usage
10+
Modern applications have modern dependencies. Whether they run on the server or in the browser, they rely on external services to get their jobs done. But along with the power to focus our business logic and distribute it across so many different points comes a fundamental weakness: The entire experience, from development, to testing, to continuous integration is coupled to the very in-the-moment states of actual deployments. This becomes problematic when those deployments are down, rate limited, under active development, or not functioning as expected in any way.
11+
12+
Simulacrum removes these constraints from your process by allowing you to simulate external dependencies with a very high degree of reality.
2713

28-
Simulacrum is based on a client server architecture. The server can hold
29-
any number of simulations which you can create and control via the
30-
client. The following examples use JavaScript, but under the hood it
31-
is just connects over HTTP and so can be used from any language.
14+
## Usage
3215

33-
To create a simulation in a simulacrum server with one of its
34-
available simulators. In this case, we'll assume that there is an
35-
`auth0` simulator on the server that we can use to create a simulation.
16+
Simulacrum is based on a client server architecture. The server can hold any number of simulations which you can create and control via the client. The following examples use JavaScript, but under the hood it is just connects over HTTP and so can be used from any language.
3617

18+
To create a simulation in a simulacrum server with one of its available simulators. In this case, we'll assume that there is an `auth0` simulator on the server that we can use to create a simulation.
3719

3820
``` javascript
3921
import { Client, createClient } from '@simulacrum/client';
@@ -49,23 +31,23 @@ let simulation = await client.createSimulation("auth0");
4931
//
5032
```
5133

52-
The resulting simulation has a list of service endpoints that you can
53-
use to configure whatever things needed for `auth0`.
34+
The resulting simulation has a list of service endpoints that you can use to configure whatever things needed for `auth0`.
5435

55-
To create a user that you can log in as, you would run the `person`
56-
scenario. This will create a person with realistic data.
36+
To create a user that you can log in as, you would run the `person` scenario. This will create a person with realistic data.
5737

5838
``` javascript
5939
let person = await client.given(simulation, "person");
60-
person.name //=> Paul Waters
61-
person.email // => Paul
40+
person.name // => Paul Waters
41+
person.email // => paul.waters@gmail.com
6242
```
6343

6444
## Development
6545

46+
```
6647
$ npm install
6748
$ npm run build
6849
$ npm test
50+
```
6951

7052
<!--
7153
## Testing

packages/client/README.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# @simulacrum/client
22

3-
A JavaScript client to control a `@simulacrum/server` over HTTP from
4-
inside your testcases, preview applications, and local development
5-
environment.
3+
A JavaScript client to control a `@simulacrum/server` over HTTP from inside your testcases, preview applications, and local development environment.
64

75
https://github.com/thefrontside/simulacrum

packages/server/README.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# @simulacrum/server
22

3-
Server capable of running multiple concurrent simulations that can be
4-
controlled by test cases, preview apps, and local developer environments.
3+
Server capable of running multiple concurrent simulations that can be controlled by test cases, preview apps, and local developer environments.
54

65
https://github.com/thefrontside/simulacrum

packages/ui/README.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,17 +4,14 @@ A Web application to manage a simulacrum server
44

55
### Development
66

7-
To start the web application in development mode, first start your
8-
`@simulacrum/server`. For example to start the dev server on port
9-
5000, run from the server directory:
7+
To start the web application in development mode, first start your `@simulacrum/server`. For example to start the dev server on port 5000, run from the server directory:
108

119
``` shell
1210
> PORT=5000 npm start
1311
Simulation server running on http://localhost:5000
1412
```
1513

16-
Now you can start your development client and point it at the
17-
development server. from the `packages/ui` directory:
14+
Now you can start your development client and point it at the development server. from the `packages/ui` directory:
1815

1916
```
2017
> npm start

0 commit comments

Comments
 (0)