/
Avocado Functional test cases with NVMe

Avocado Functional test cases with NVMe

Aug 26, 2021

List of functional tests available as of 10/31/2018

Folder

Test Files

Folder

Test Files

Pool

BadConnect.yaml – FAIL – DAOS issue - https://daosio.atlassian.net/browse/DAOS-1691

BadCreate.yaml – FAIL – DAOS issue- https://daosio.atlassian.net/browse/DAOS-1705

BadEvict.yaml – FAIL - TEST issue - https://daosio.atlassian.net/browse/DAOS-1709 - This looks like Test defect. After investigation this can be assigned to Dev, if it's DAOS side issue.

BadExclude.yaml - FAIL - TEST issue - https://daosio.atlassian.net/browse/DAOS-1711

BadQuery.yaml - PASS

ConnectTest.yaml – FAIL - Test issue - https://daosio.atlassian.net/browse/DAOS-1718 - Tried with socket with NVMe and it's working fine.

DestroyRebuild.yaml – Need 6 Serves - FAIL - This will not work until we get pool destroy fix https://daosio.atlassian.net/browse/DAOS-1811 There is existing defect open for same test https://daosio.atlassian.net/browse/DAOS-989

DestroyTests.yaml - Need 6 Servers - FAIL - This will not work until we get pool destroy fix https://daosio.atlassian.net/browse/DAOS-1811 https://daosio.atlassian.net/browse/DAOS-1691

EvictTest.yaml - PASS

GlobalHandle.yaml - PASS

InfoTests.yaml - FAIL - DAOS issue - https://daosio.atlassian.net/browse/DAOS-1722

MultipleCreatesTest.yaml - PASS

MultiServerCreateDeleteTest.yaml - PASS

Permission.yaml - FAIL - DAOS issue - https://daosio.atlassian.net/browse/DAOS-1722

PoolSvc.yaml – FAIL - TEST issue - https://daosio.atlassian.net/browse/DAOS-1242

RebuildNoCap.yaml – Need 6 Servers - FAIL - TEST issue - https://daosio.atlassian.net/browse/DAOS-1846 , Now the Pool should be too full to start a rebuild and it should return rebuild failure error as per test. Confirm with Scott on expected behavior of tests.

RebuildTests.yaml – Need 6 Servers - DAOS issue - FAIL - https://daosio.atlassian.net/browse/DAOS-1828

RebuildWithIO.yaml – PASS - Need 6 Servers

SimpleCreateDeleteTest.yaml - PASS

Object

ArrayObjTest.yaml - PASS

CreateManyDkeys.yaml - PASS

ObjFetchBadParam.yaml - PASS

ObjUpdateBadParam.yaml - PASS

PunchTest.yaml - PASS

Container

Open.yaml - PASS - It's required some minor modification in Tear down code to work with NVMe, disconnecting the pool before destroying it works fine in SCM but not in NVME https://daosio.atlassian.net/browse/DAOS-1691. Eventually test case will need update.

OpenClose.yaml - Need 4 Servers - FAIL - Test Issue - https://daosio.atlassian.net/browse/DAOS-1799

ContainerAsync.yaml – Need 4 servers - PASS - DAOS issue - https://daosio.atlassian.net/browse/DAOS-1811 - Defect Verified.

GlobalHandle.yaml - PASS

Attribute.yaml - PASS

BasicEpochTest.yaml - PASS

Delete.yaml – FAIL -test Issue - https://daosio.atlassian.net/browse/DAOS-1789 - Make sure to use 1G pool size for NVMe. Add pool.disconnect() if this test required to be ran with NVMe

FullPoolContainerCreate.yaml - FAIL - Test Issue - https://daosio.atlassian.net/browse/DAOS-1768 - This test will not work with NVMe as minimum size of pool on NVMe is 1G where in test it's 16MB


SimpleCreateDeleteTest.yaml – Need 6 Servers - PASS - Pool Destroy issue observer for which https://daosio.atlassian.net/browse/DAOS-1811 - Verified Defect.

io

IorSingleServer.yaml - PASS - DAOS issue - DAOS-1791: Running IOR command back to back is getting failed with error "no space on storage target"Resolved - Need to update the TC if it fails again but it's working OK. Increase the pool size or put some delay in between IOR as per defect

repo

RepoTest.yaml - Not Executed - It's not DAOS function test

server

ServerLaunch.yaml - Not Executed - It's only server start which works in TestSetup() part of most of the test cases

unittest

Unittest.yaml - Not Executed - It's Unit tests so not needed to run against NVMe