Categories:
Aura QA Tool troubleshooting guide
Find the most common problems and errors that may happen in the QA tool execution and the corresponding fixing procedures
Introduction
The most common problems and errors found in the QA Tool management have been included in this document.
- Problems related to users’ configuration in Telefónica Kernel.
- Problems related to a mismatch between expected and received response.
- Problems related to users’ config file (
authorization_id).
Errors related to users’ configuration in Kernel
Error definition
The configuration of the user in Kernel is not the appropriated one.
An example of this type of error is included below:
AssertionError: FAILED SUB-STEP: Given I have a users.common.prepaid msisdn logged with phone_number
Substep info: Assertion Failed: INVALID USER: Contract type is not correct for user 'users.common.prepaid' with user_id '42005239175568025518978' and msisdn '+4917687465961'.
Expected: prepaid. Current: None
Fixing procedure
This error means that the tests are using the users.common.prepaid user set-up in:
~/[project_folder]/aura-tests/acceptance/settings/[country_code]/[environment]-users.json
Check the document Users’ configuration in order to know how to configure users.
"users": {
"default": "user8",
"common": {
"postpaid": "user4",
"control": "",
"prepaid": "user6"
},
In the example, the user has different configurations in Kernel. You will find the information for this user in the following file once the tests have run:
~/[project_folder]/aura-tests/acceptance/_output/users/[country_code]/[userid].json
Problems related to a mismatch between expected response and received response
Error definition
The test is expecting for a different sentence than the one received.
An example of this type of error is included below:
AssertionError: FAILED SUB-STEP: Then the element "aura_response" contains a response to the question "2" with a text matching one of "none:none.fallbackanswer"
Substep info: Assertion Failed: Question asked: "2"
Current response "Vertragskunde:
Um deinen aktuellen Tarif mit weiteren Geräten nutzen zu können, kannst du online in Mein o2 eine oder mehrere zusätzliche SIM-Karten, die sogenannte Multicard, bestellen.
Prepaidkunde:
Wenn du mit der Multicard mehrere Geräte mit ein- und derselben Rufnummer nutzen möchtest, ist das bei o2 ausschließlich mit einem Laufzeitvertrag möglich. Eine Multi-SIM ist für o2 Prepaid derzeit leider nicht erhältlich." doesn´t match any of the
Expected responses: ['Diese Frage kann ich dir leider noch nicht beantworten.', 'Diese Frage kann ich dir leider noch nicht beantworten.', 'Diese Frage kann ich dir leider noch nicht beantworten.', 'Diese Frage kann ich dir leider noch nicht beantworten.']
First difference: received "Vertragsku" and expected "Diese Frag"
Fixing procedure
When this error is not a bug, the reason can probably be:
- The
poeditor_termsfile used in the QA Tool is different from the one used in the environment or one of the resources is not the same.
In this case, you should update thepoeditor_terms_[language]_[country_code].jsonwith the latest export from the POEditor website. In order to fix this error, add the sentence topoeditor_terms_[language_code]_[country_code].json, in the section described by the error explanation.
For example:
{
"term": "Un poco de música nunca está de más.",
"definition": "Ein bisschen Musik schadet nie.",
"context": "Transversal",
"term_plural": "",
"reference": "none:none.fallbackanswer",
},
Error related to users’ config file (mandatory authorization_id)
Error definition
Check the authorization_id field in the properties.json file. This parameter can have the values optional or mandatory.
The default value for authorization_id is optional.
"4p": {
"authorization_id": "mandatory"
}
The most common problems related to authorization_id are shown in the following sections.
uid/email not correctly configured
When authentication by uid or email is used in a test, but is not correctly configured in the users’ file, this error may be displayed:
Assertion Failed: Configured user "users.default" does not contain "uid" field in users file. May be one of these identities should be used: [{'uid': '69828310687261441744979'}, {'uid': None}, {'phone_number': '+4917625262904'}]
The way to solve it is to add the missing data in the users' file (in the example above, the uid field) or add SKIP value to avoid authentication failures, so the tests with this user + authentication method, are skipped).
Login error
In case of a login error, this error may be displayed in logs:
ValueError: Missing query parameter code in url:
- URL: https://login-crt.o2online.de/sso/UI/Login
- BODY: <html class=" no-touch transition transform animation mediaquery localstorage placeholder"><head><meta name="viewport"… (rest of HTML code of error page)
If possible, add both fields, uid and email or password.
In case it is impossible to obtain the uid and/or email of the user, you can add SKIP value to avoid authentication failures (Note that tests with this user + authentication method are skipped).
MSISDN error
When authentication by phone number is used in a test, but is not correctly configured in the users’ file, this error may be displayed:
File "/home/rgl/virtualenvs/aura-tests-py3/lib/python3.7/site-packages/selenium/webdriver/support/wait.py", line 80, in until
raise TimeoutException(message, screen, stacktrace)
selenium.common.exceptions.TimeoutException: Message:
Page element of type 'InputText' with locator ('id', 'code') not found or is not visible after 15 seconds
The way to solve it is to add the missing data in the users’ file, in this case, the msisdn field.
Another error may occur when the authentication code is not received via SMS in the second step. In this scenario, ask the QA Global Team for the system method to obtain the authentication code via SMS automatically):
File "/home/rgl/virtualenvs/aura-tests-py3/lib/python3.7/site-packages/qa4pcommons/utils/simgrid.py", line 57, in find_new_sms_code
raise ValueError(msg.format(self.phone_number))
ValueError: New message not found for phone_number: "+4917625262904"
Error fetching data from Telefónica Kernel APIs
If there is a problem getting info from Kernel APIs, this error may be displayed:
Assertion Failed: Get Aura id response does not contain aura_id field
In test logs, the following warning may be displayed (in this case, there is a server problem getting info from a user in Kernel):
INFO 2021-05-12 08:54:23,254 [authentication] Getting aura id from 4P API
INFO 2021-05-12 08:54:23,262 [data_4p] >>>>>>>>>>>>>>>>>>>>> Request aura_id 4TH PLATFORM >>>>>>>>>>>>>>>>>>>
DEBUG 2021-05-12 08:54:23,262 [data_4p] Curl request: curl "https://api.de-pre.baikalplatform.com/aura-services/v1/users/aura-id" -s -H "Authorization: Bearer eyJraWQiOiI1NDJhMzI4MjViZjBiZjMwODU2N2Q4ZTVjMTNmNWE4ZTNmNjE0ZmZjIiwidHlwIjoiSldUIiwiYWxnIjoiUlMyNTYifQ.eyJzdWIiOiI2OTgyODMxMDY4NzI2MTQ0MTc0NDk3OSIsImF1dGhvcml6YXRpb25faWQiOiJlZGE2MmI0YS03YzQxLTQwOTUtOTk3Yy1iMjM5MDgxMDc0ZTkiLCJwdXJwb3NlIjoiY3VzdG9tZXItc2VsZi1zZXJ2aWNlIGlkZW50aWZ5LWN1c3RvbWVyIiwiaXNzIjoiaHR0cHM6XC9cL2F1dGguZGUtcHJlLmJhaWthbHBsYXRmb3JtLmNvbVwvIiwiYXV0aGVudGljYXRpb25fY29udGV4dCI6W3siaWRlbnRpZmllciI6IjY5ODI4MzEwNjg3MjYxNDQxNzQ0OTc5IiwidHlwZSI6InVpZCJ9XSwiYWN0aXZlIjp0cnVlLCJjbGllbnRfaWQiOiJhdXJhLWJvdCIsImlkZW50aWZpZXJfYm91bmRfc2NvcGUiOltdLCJhdWQiOiJodHRwczpcL1wvYXBpLmRlLXByZS5iYWlrYWxwbGF0Zm9ybS5jb20iLCJzY29wZSI6ImV2ZW50LWxvdy1kYXRhLXJlYWQgYXVyYWlkLXJlYWQgdXNlcnByb2ZpbGUtcmVhZCBldmVudC1zdWJzY3JpcHRpb24tdHlwZS1taWdyYXRpb24tcmVhZCBldmVudC1sb3ctdm9pY2UtcmVhZCBhdXRoZW50aWNhdGlvbi1pbmZvcm1hdGlvbi1yZWFkIHNpbmdsZS1hY2Nlc3Mtc2Vzc2lvbnMtd3JpdGUgZXZlbnQtYmFyLWFsZXJ0LXJlYWQgZXZlbnQtbm8tZGF0YS1yZWFkIHN1YnNjcmliZWQtcHJvZHVjdHMtcmVhZCBtb2JpbGUtYmFsYW5jZS1yZWFkIGV2ZW50LW5vLWJhbGFuY2UtcmVhZCBzdWJzY3JpYmVkLXByb2R1Y3RzLXVzZXItcmVhZCBpbnZvaWNpbmctcGhvbmUtbnVtYmVyLXJlYWQgZXZlbnQtYXBwb2ludG1lbnQtcmVtaW5kZXItcmVhZCBldmVudC1pbnZvaWNlLWRlYml0LXJlYWQgZXZlbnQtcGF5bWVudC1hbGVydC1yZWFkIGF1cmFpZC13cml0ZSBtb2JpbGUtcXVvdGEtcmVhZCBzdWJzY3JpYmVkLXByb2R1Y3RzLXBob25lLW51bWJlci1yZWFkIGV2ZW50LW5vLXZvaWNlLXJlYWQgbm90aWZpY2F0aW9ucy1yZWFkIHRpbWVsaW5lLXJlYWQgZXZlbnQtaGlnaC1zcGVuZC1hbGVydC1yZWFkIGV2ZW50LWRpc2Nvbm5lY3Rpb24tYWxlcnQtcmVhZCBldmVudC1pbnZvaWNlLXBheW1lbnQtZHVlLXJlYWQgbW9iaWxlLWJhbGFuY2UtdG9wLXVwLXdyaXRlIGV2ZW50LWxvdy1iYWxhbmNlLXJlYWQgaW52b2ljaW5nLXVzZXItcmVhZCBpc3N1ZXMtY3JlYXRlIG1vYmlsZS1iYWxhbmNlLXRvcC11cC1yZWFkIGludm9pY2luZy1yZWFkIGV2ZW50LWludm9pY2UtcmV0YWluZWQtcmVhZCBpc3N1ZXMtcmVhZCBldmVudC1pbnZvaWNlLWNoYXJnZS1yZWFkIiwiYWNyX3ZhbHVlcyI6IjMiLCJleHAiOjE2MjA4MDYwNjMsImlhdCI6MTYyMDgwMjQ2MywianRpIjoiM2MyY2QzYTEtM2U0MS00ODE2LTkxMTgtZmZkOGM2MDRlYmU4In0.NNQSe_yD3U8togdNGhVXvO9hTlKJtgflmNmpQzLmucGBSmujmcSn4kWSYRkVOGRakzf6cRSGh9CNfuH0iWYqQrFVXlzDWadOkAzkZnb-7QPjZ1FclTCFe1EPn_JM8qcpERxB5IM_9a-M0MvMQ7-O0rpnE5V7ZG0Lnu2V_LO8Id-f1_AjLtnkNGXdK3n16R1Gzp4OzIANx28EGq7Wu2Y-5BfcMT8spdsQ7pKWF7O_aXOSxJmQnEKb2ZAzVCYekjpEUtic7IYP5jh4l1zQMy0_81IkdQPMdOAFA2LON4IgkF2RoXSilgS27zFkBWQkyj5bM6FsFeqswMaBF6DUEWbPGQ"
WARNING 2021-05-12 08:54:24,721 [data_4p] Error response for aura_id api with status 503: {'message': 'name resolution failed'}
Check the document Users’ configuration in order to know how to configure users.