<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/test/py/tests/test_fs/test_basic.py, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-04-09T19:34:15Z</updated>
<entry>
<title>test: fs: Add filesystem integrity checks</title>
<updated>2019-04-09T19:34:15Z</updated>
<author>
<name>Jean-Jacques Hiblot</name>
</author>
<published>2019-02-13T11:15:23Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=290100583dc70185e76ddaa00c1a50abd162a5ad'/>
<id>urn:sha1:290100583dc70185e76ddaa00c1a50abd162a5ad</id>
<content type='text'>
We need to make sure that file writes,file creation, etc. are properly
performed and do not corrupt the filesystem.
To help with this, introduce the assert_fs_integrity() function that
executes the appropriate fsck tool. It should be called at the end of any
test that modify the content/organization of the filesystem.
Currently only supports FATs and EXT4.

Signed-off-by: Jean-Jacques Hiblot &lt;jjhiblot@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>test: Add a 'make qcheck' target for quicker testing</title>
<updated>2018-11-29T16:30:05Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2018-11-18T15:14:29Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=499fde5c23921add3cf95fecfe0b03d717d5a33b'/>
<id>urn:sha1:499fde5c23921add3cf95fecfe0b03d717d5a33b</id>
<content type='text'>
At present tests are quite slow to run, over a minute on my machine. This
presents a considerable barrier to bisecting for failures.

The slowest tests are the filesystem ones and the buildman --fetch-arch
test. Add a new 'qcheck' target that skips these tests. This reduces test
time down to about 40 second, still too long, but bearable.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>test/py: convert fs-test.sh to pytest</title>
<updated>2018-09-23T19:55:30Z</updated>
<author>
<name>AKASHI Takahiro</name>
</author>
<published>2018-09-11T06:59:19Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=de8106c198b442f8363557006c13a7807d972552'/>
<id>urn:sha1:de8106c198b442f8363557006c13a7807d972552</id>
<content type='text'>
In this commit, the same set of test cases as in test/fs/fs-test.sh
is provided using pytest framework.
Actually, fs-test.sh provides three variants:"sb" (sb command), "nonfs"
(fatxx and etc.) and "fs" (hostfs), and this patch currently supports
only "nonfs" variant; So it is not a replacement of fs-test.sh for now.

Simple usage:
  $ py.test test/py/tests/test_fs [&lt;other options&gt;]

You may also specify filesystem types to be tested:
  $ py.test test/py/tests/test_fs --fs-type fat32 [&lt;other options&gt;]

Signed-off-by: AKASHI Takahiro &lt;takahiro.akashi@linaro.org&gt;
Signed-off-by: Alexander Graf &lt;agraf@suse.de&gt;
</content>
</entry>
</feed>
