1. OPNFV Fraser release note for Functest

1.1. Abstract

This document contains the release notes of the Functest project.

1.2. OPNFV Fraser Release

Functest deals with functional testing of the OPNFV solution. It includes test cases developed within the project, test cases developed in other OPNFV projects and it also integrates test cases from other upstream communities.

1.2.1. OpenStack

The internal test cases are:

  • connection_check
  • api_check
  • snaps_health_check
  • vping_ssh
  • vping_userdata
  • tempest_smoke_serial
  • rally_sanity
  • refstack_defcore
  • patrole
  • odl
  • snaps_smoke
  • neutron_trunk
  • tempest_full_parallel
  • rally_full
  • cloudify_ims
  • vyos_vrouter
  • juju_epc

The OPNFV projects integrated into Functest framework for automation are:

  • doctor
  • bgpvpn
  • odl-sfc
  • barometer
  • fds
  • parser

1.2.2. Kubernetes

The internal test cases are:

  • k8s_smoke
  • k8s_conformance

The OPNFV projects integrated into Functest framework for automation are:

  • stor4nfv
  • clover

1.3. Release Data

Project functest
Release designation Fraser
Repository branch stable/fraser
Repository tag opnfv-6.2.0
Release date June 29th 2018

1.5. Version change

1.5.1. New test cases

  • neutron_trunk
  • patrole
  • juju_epc
  • k8s_smoke
  • k8s_conformance
  • stor4nfv
  • clover

1.5.2. Key changes

  • update test cases and containers to OpenStack Pike
  • move the framework into a separate project: Xtesting
  • ease running all containers thanks to default values
  • clean interfaces with OPNFV Installers and Features
  • rewrite all vnfs to allow multiple tests in parallel
  • fully support non-default region names and Keystone v3 domains
  • refactor all tempest-based test cases (e.g. refstack_defcore)
  • remove obsolete OpenStack and Functest utils
  • verify all changes via doc8 and yamllint too
  • generate reports for all tempest-based test cases

1.5.3. Key benefits

  • the enduser can run all tests by setting only one input (EXTERNAL_NETWORK)
  • the developer can only work on the test suites without diving into CI/CD integration
  • both OpenStack and Kubernetes deployments can be verified
  • Functest test cases are trustable as they meet the best coding rules (unit tests, coverage, linters, etc.)
  • Functest can be reused in other projects (e.g. ONS: Re-using OPNFV framework tests for LFN projects)

1.5.4. Code quality

  • pylint: ~9.5/10
  • code coverage: ~70%