kvazar
/
kevacoin
mirror of https://github.com/kvazar-network/kevacoin.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Update readme with better link syntax (for clickable links) and better readability.

0.8
Chuck LeDuc Díaz 12 years ago
parent
33edd0a477
commit
da986f793d
1 changed files with 3 additions and 3 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 6
      README.md

6
README.md
Unescape View File

@ -70,8 +70,8 @@ Unit tests for the GUI code are in `src/qt/test/`. To compile and run them:
Every pull request is built for both Windows and Linux on a dedicated server, Every pull request is built for both Windows and Linux on a dedicated server,
and unit and sanity tests are automatically run. The binaries produced may be and unit and sanity tests are automatically run. The binaries produced may be
used for manual QA testing -- a link to them will appear in a comment on the used for manual QA testing — a link to them will appear in a comment on the
pull request posted by 'BitcoinPullTester'. See `https://github.com/TheBlueMatt/test-scripts` pull request posted by [BitcoinPullTester](https://github.com/BitcoinPullTester). See https://github.com/TheBlueMatt/test-scripts
for the build/test scripts. for the build/test scripts.
### Manual Quality Assurance (QA) Testing ### Manual Quality Assurance (QA) Testing
@ -79,4 +79,4 @@ for the build/test scripts.
Large changes should have a test plan, and should be tested by somebody other Large changes should have a test plan, and should be tested by somebody other
than the developer who wrote the code. than the developer who wrote the code.
See `https://github.com/bitcoin/QA/` for how to create a test plan. See https://github.com/bitcoin/QA/ for how to create a test plan.

Write Preview
Loading…
Cancel
Save