Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 55 Next »

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

FolderTest Files

Pool

BadConnect.yaml – FAIL – DAOS issue -

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

BadCreate.yaml – FAIL – DAOS issue- Unable to locate Jira server for this macro. It may be due to Application Link configuration.

BadEvict.yaml – FAIL - TEST issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration. - This looks like Test defect. After investigation this can be assigned to Dev, if it's DAOS side issue.

BadExclude.yaml - FAIL - TEST issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration.

BadQuery.yaml - PASS

ConnectTest.yaml – FAIL - Test issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration. - 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 Unable to locate Jira server for this macro. It may be due to Application Link configuration.

DestroyTests.yaml - Need 6 Servers

EvictTest.yaml - PASS

GlobalHandle.yaml - PASS

InfoTests.yaml - FAIL - DAOS issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration.

MultipleCreatesTest.yaml - PASS

MultiServerCreateDeleteTest.yaml - PASS

Permission.yaml - FAIL - DAOS issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration.

PoolSvc.yaml – FAIL - TEST issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration.

RebuildNoCap.yaml – Need 6 Servers

RebuildTests.yaml – Need 6 Servers

RebuildWithIO.yaml – 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 Unable to locate Jira server for this macro. It may be due to Application Link configuration. . Eventually test case will need update.

OpenClose.yaml - Need 4 Servers - FAIL - Test Issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration.

ContainerAsync.yaml – Need 4 servers - FAIL - DAOS issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration.

GlobalHandle.yaml - PASS

Attribute.yaml - PASS

BasicEpochTest.yaml - PASS

Delete.yaml – FAIL -test Issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration. - 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 - Unable to locate Jira server for this macro. It may be due to Application Link configuration. - 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 Unable to locate Jira server for this macro. It may be due to Application Link configuration. is open

io

IorSingleServer.yaml - FAIL - DAOS issue - Unable to locate Jira server for this macro. It may be due to Application Link configuration.

repoRepoTest.yaml - Not Executed - It's not DAOS function test
serverServerLaunch.yaml - Not Executed - It's only server start which works in TestSetup() part of most of the test cases
unittestUnittest.yaml - Not Executed - It's Unit tests so not needed to run against NVMe

Current Automation tests with NVMe:

Option 1: 

  1. We can identified the *.yaml file to be ran with NVMe
  2. Update the NVMe config parameter in yaml file.
  3. Update the tags to run on *.yaml NVMe hardware.

Option 2:

  1. We can add new argument to ./launch script for example ./launch TAG_TEST NVMe. This will provide flexibility to run tests against any SCM.
  2. Launch script will setup the server if NVMe is enabled, calling NVMe.setup() from ServerUtils.py
  3. Test will be ran with avocado run <TAG_TEST>
  4. Launch script will cleanup the server if NVMe is enabled, calling NVMe.cleanup() from ServerUtils.py



  • No labels