summaryrefslogtreecommitdiffstats
path: root/README.md
blob: d9e453709de95f2e58e2695376b09a8ee1bf30d4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
# Glusto Tests

`glusto-tests` repo contains automated testcases for testing gluster software.
It provides the Libraries/Modules necessary for automating the gluster tests.
Latest Code for this repo is managed on review.gluster.org

The Libraries/Modules/Tests in glusto-tests are written using the `glusto`
framework. TestCases in glusto-tests can we written/run using standard
PyUnit, PyTest or Nose methodologies as supported by `glusto` framework.

Refer the [glusto-doc](http://glusto.readthedocs.io/en/latest/) for info on `glusto` framework.
Issues need to be filled against the [Github](https://github.com/gluster/glusto-tests/issues) repo.

To automate/run glusto-tests we need to install the following packages:
---------------------------------------------------------------------
-   glusto
-   glustolibs-gluster
-   glustolibs-io
-   glustolibs-misc
-   gdeploy

How to install glusto:
----------------------
One can use either of the two methods.

-   using pip

        # pip install --upgrade git+git://github.com/loadtheaccumulator/glusto.git

-   using git

        # git clone https://github.com/loadtheaccumulator/glusto.git
        # cd glusto
        # python setup.py install

For more info refer the [docs](http://glusto.readthedocs.io/en/latest/userguide/install.html).

How to install the glustolibs-gluster, glustolibs-io and glustolibs-misc libraries:
----------------------------------------------------------------------------------------------
    # git clone http://review.gluster.org/glusto-tests
    # cd glusto-tests/glustolibs-gluster
    # python setup.py install
    # cd ../../glusto-tests/glustolibs-io
    # python setup.py install
    # cd ../../glusto-tests/glustolibs-misc
    # python setup.py install

How to install gdeploy:
--------------------------------
-   Install latest version of gdeploy from the following [link](https://copr.fedorainfracloud.org/coprs/sac/gdeploy/package/gdeploy/).

To install glusto-tests dependencies:
--------------------------------------------------
- `python-docx` needs to be installed when we run IO's and validates on client node.
    - To install run :

			    # curl "https://bootstrap.pypa.io/get-pip.py" -o "get-pip.py"
			    # python get-pip.py
			    # pip install --pre python-docx

- `arequal` needs to be installed on all servers and clients.
	- To install download the below repo into /etc/yum.repos.d/

			# wget https://copr.fedorainfracloud.org/coprs/nigelbabu/arequal/repo/epel-7/nigelbabu-arequal-epel-7.repo
			# yum install arequal

Pre-requisites to run glusto-tests:
----------------------------------------------
- Make sure glusto, glusto-tests  are installed on the node from where you would want to run the gluster tests.
- Running Gluster Cluster( 6 Servers and 2 Clients )
- Gluster client packages should be installed on Clients
- Setup passwordless ssh from the glusto-tests management node to all.
- Install glusto-tests dependencies on servers and clients.
- Setup bricks on all servers:
	- To create bricks refer to [doc](https://gluster.readthedocs.io/en/latest/Administrator%20Guide/formatting-and-mounting-bricks/)

Note:

	- To run cifs protocol:
		1.CIFS packages need to be installed on the server
		2.Samba services need to be ACTIVE
		3.cifs-utils need to be installed on the client
	- To run nfs protocol, nfs packages must be installed on server and client

 For more info how to run glusto-tests from the scratch including creating OS, server, etc.. refer [link](https://github.com/gluster/glusto-tests/blob/master/docs/userguide/HOWTO)

How to run the test case:
----------------------------------
-  Update the information about the servers, clients, servers_info, client_info on the [config_file](https://github.com/gluster/glusto-tests/blob/master/tests/gluster_basic_config.yml), this information is enough to run all test cases. But if you need to override the default values of volumes, mount.. etc which is defined in gluster_base_class then use  [config](https://github.com/gluster/glusto-tests/blob/master/tests/gluster_tests_config.yml) and update the information accordingly.
Refer the following for more info [link](http://glusto.readthedocs.io/en/latest/userguide/configurable.html).

-   glusto-tests are run using the `glusto` command available after installing the glusto framework. The various options to run tests as provided by glusto framework: PyUnit Tests, PyTest Tests, Nose Tests.
The most common used is Pytest.
	- **Running PyTest Tests**
		- To run all tests that are marked with tag 'bvt':

				# glusto -c config.yml --pytest='-v -x tests -m bvt'
		- To run all tests that are under bvt folder:

				# glusto -c config.yml --pytest='-v -s bvt/'
		- To run a single test case:

				# glusto -c config.yml --pytest='-v -s -k test_demo1'

For more info about running tests on PyUnit, Pytest and Nose Tests, refer the [docs](http://glusto.readthedocs.io/en/latest/userguide/glusto.html#options-for-running-unit-tests).

Writing tests in glusto-tests:
----------------------------------
- `tests` directory in glusto-tests contain testcases. Testcases are written as component wise.
Testcases name and file name should should start with **test_**.

- TestCases in glusto-tests can be written using standard PyUnit, PyTest or Nose methodologies as supported by `glusto` framework.
	- One can follow the [PyUnit](http://glusto.readthedocs.io/en/latest/userguide/unittest.html) docs to write PyUnit tests, or [PyTest](http://glusto.readthedocs.io/en/latest/userguide/pytest.html) docs to write PyTest tests, or [Nose](http://glusto.readthedocs.io/en/latest/userguide/nosetests.html) docs to write Nose tests.

**While writing testcases or libraries follow:**

- Please follow the [PEP008 style-guide](https://www.python.org/dev/peps/pep-0008/).
- Makes sure all the pylint and pyflakes error are fixed.
	For example

		- C0326: Exactly one space required around assignment
		- C0111: Missing module doc-string (missing-doc string)
		- W: 50: Too long line

	For more information on [pylint](https://docs.pylint.org/en/1.6.0/tutorial.html) and on [pyflakes](http://flake8.pycqa.org/en/latest/index.html).
	We can check for pyflakes and pylint errors:
	```
	# flake8 <test_script.py>
	or
	# flake8 <path_to_directory>
	# pylint -j 4 --rcfile=/glusto-tests/.pylintrc <test_script.py>
	```
- Optimize the code as much as possible. Eliminate the repetitive steps, write it has separate function.
- Use proper python standards on returning values. This style guide is a list of do's and don’ts for[ Python programs](http://google.github.io/styleguide/pyguide.html).
- Add docstring to every function you write
For example: This is an example of a module level function
  ```
	   def module(param1, param2):
       """
       Explain what the module function does in breif

       Args:
           param1: The first parameter.
           param2: The second parameter.

       Returns:
           The return value of the function.
       """
  ```

- Make sure the log messages are grammatically correct and have no spelling mistakes.

- Comment every step of the test case/libraries, log the test step, test result, failure and success.
For example:
   ```
   def test_peer_status(self):
       # peer status from mnode
       g.log.info("Get peer status from node %s", self.mnode)
       ret, out, err = peer_status(self.mnode)
       self.assertEqual(ret, 0, "Failed to get peer status from node %s: %s" % (self.mnode, err))
       g.log.info("Successfully got peer status from node %s:\n%s", self.mnode, out)
   ```


- Don't not use print statements in test-cases/libraries because prints statements are not captured in log files. Use logger functions to dump messages into log file.

For more info how to write testcases [developing-guide](https://github.com/gluster/glusto-tests/blob/master/docs/userguide/developer-guide.rst)

Logging:
--------------
Log file name and Log level can be passed as argument to glusto command while
running the glusto-tests. For example:

    # glusto -c 'config.yml' -l /tmp/glustotests_bvt.log --log-level DEBUG --pytest='-v -x tests -m bvt'

One can configure log files, log levels in the testcases as well. For details
on how to use glusto framework for configuring logs in tests Refer the following [docs](http://glusto.readthedocs.io/en/latest/userguide/loggable.html).

Default log location is: `/tmp/glustomain.log`

Note: When using `glusto` via the Python Interactive Interpreter,
the default log location is `/tmp/glusto.log`.