Age | Commit message (Collapse) | Author | Files | Lines |
|
there is no error_message method on onapsdk exception
as a consequence we may raise a new excpetion when catching sdk
exception leading to the non generation of the report
Issue-ID: TEST-332
Signed-off-by: morganrol <morgan.richomme@orange.com>
Change-Id: I42d1413ef142e29eeafdfe701f136ae45b097de4
|
|
Catch onaptests and onapsdk exceptions in scenario to generate test report if test fails
Issue-ID: INT-1852
Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl>
Change-Id: Id9772fea10dc5aa323437e72c6fe5ddb4c6caabb
|
|
Use Python SDK exceptions.
Issue-ID: TEST-302
Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl>
Change-Id: I76996817c0d7b91c0214ad521c3768682ff07e83
|
|
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
|
|
Issue-ID: TEST-255
Signed-off-by: andreasgeissler <andreas-geissler@telekom.de>
Change-Id: I86b34c0980cee7a5824231591a60d1f50dfe4f37
Signed-off-by: mrichomme <morgan.richomme@orange.com>
|