Skip to content

Update test information in readme #214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 17, 2017
Merged

Update test information in readme #214

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -350,8 +350,7 @@ Destroying models may result in errors due to foreign key integrity. First delet

## Running tests

The tests in this repository are mainly integration tests, meaning you will need
to run them using our preconfigured test server.
The tests in this repository are mainly integration tests, meaning you will need to run them using our preconfigured test server.

1. Ask a core developer for instructions on how to set up test server
credentials on your machine
Expand All @@ -378,9 +377,11 @@ In ```test\init.js```, change the value of ```config``` to be pointing to the lo
};
```

2. (`Linux Only`) `CI=true PGHOST=localhost PGPORT=<pgport> PGDATABASE=<dbname> PGUSER=<username> PGPASSWORD=<password> npm test`

__Troubleshooting__

When running npm test, it runs the ```pretest.js``` which eventually runs ```schema.sql``` to set up the database and tables.
When running `npm test`, it runs the ```pretest.js``` which eventually runs ```schema.sql``` to set up the database and tables.
If there is problem, you can run the ```schema.sql``` manually. To do this:

1. Go to SQL Shell (psql)
Expand Down