Skip to content

Commit 31a397c

Browse files
committed
[FAB-5198] Update README
Add the PATH to the README and update to mention the helpful tools information in the how to contribute section. Change-Id: Ib33bc2d80c15c13776e65bfc3bd413d7283c343a Signed-off-by: Latitia M Haskins <latitia.haskins@gmail.com>
1 parent 9b14b3f commit 31a397c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

test/feature/README.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ The docker images for ``peer``, ``orderer``, ``kafka``, and ``zookeeper`` are ne
128128
=========================
129129
Building tool executables
130130
=========================
131-
The **configtxgen** and **cryptogen** tools are used when bootstrapping the networks in these tests. As a result, you must perform a ``make configtxgen && make cryptogen`` in the ``/path/to/hyperledger/fabric`` directory.
131+
The **configtxgen** and **cryptogen** tools are used when bootstrapping the networks in these tests. As a result, you must perform a ``make configtxgen && make cryptogen`` in the ``/path/to/hyperledger/fabric`` directory. Be sure that the executable location is added to your PATH.
132132

133133

134134
How to Contribute
@@ -144,7 +144,7 @@ There are different ways that you can contribute in this area.
144144
===================================
145145
How Do I Write My Own Feature File?
146146
===================================
147-
The feature files are written by anyone who understands the requirements. This can be a business analyst, quality analyst, manager, developer, customer. The file describes a feature or part of a feature with representative examples of expected outcomes and behaviors. These files are plain-text and do not require any compilation. Each feature step maps to a python step implementation.
147+
The feature files are written by anyone who understands the requirements. This can be a business analyst, quality analyst, manager, developer, customer, etc. The file describes a feature or part of a feature with representative examples of expected outcomes and behaviors. These files are plain-text and do not require any compilation. Each feature step maps to a python step implementation. When choosing appropriate key phrases when writing feature files, look in the `Helpful Tools`_ section for more information.
148148

149149
The following is an example of a simple feature file:
150150

0 commit comments

Comments
 (0)