Better exception handling 30/115530/1
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>
Tue, 1 Dec 2020 16:49:31 +0000 (17:49 +0100)
committerMorgan Richomme <morgan.richomme@orange.com>
Tue, 1 Dec 2020 22:16:10 +0000 (22:16 +0000)
commit7a8cc3ff337cb471d093042345eb68d8888253e6
treea85641a2fa8e95e374655f0f20bd63cf98c9ffe1
parent3c2183191fc1a2d01b24c7e91a144dad8467cd20
Better exception handling

Instead of catching all exceptions that can occurs and miss one, let's
create a "parent" exception class for OnapTest and catch only this one.

In order to know what's the error, we also create a class attribute
(`error_message`) that gives us the reason for exception.

Issue-ID: INT-1796
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I798d8c6270c466b1d9be6511f52fd9441401c9c8
(cherry picked from commit 9c71e24adaaedd07d7e2e65922c5a3cee27318c9)
src/onaptests/scenario/basic_cnf.py
src/onaptests/scenario/basic_network.py
src/onaptests/scenario/basic_vm.py
src/onaptests/scenario/clearwater_ims.py
src/onaptests/utils/exceptions.py