[#40390] - [cypress] instructions
- Closed
- 18 Apr 2023
- Medium
- Build: 4.3-dev
- # 40390
I am getting multiple errors and I am assuming that it is partially down to my joomla installation and/or missing instructions
- Should I be running the tests on a CLEAN joomla install or can it be on ANY joomla install
- and then how can you run the installation test because joomla is already installed
- all of the API tests are failing with a 401 unauthorized on a CLEAN joomla install - is there a missing setup instructiion about this?
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
all of the API tests are failing with a 401 unauthorized
The api token is hardcoded in the api.js
File: \joomla\tests\System\support\commands\api.js
Generate your own token and paste it in. And it works. But that cannot be the intention. So I guess the api code is not finished yet.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40390.
Test instructions: https://github.com/joomla/joomla-cms/blob/4.4-dev/tests/System/README.md
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40390.
how does you posting the instructions help when I already said the instructions are missing information
I'm trying to contribute here. Perhaps I should have indicated 'issue confirmed' better.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40390.
yes - thankyou
| Status | New | ⇒ | Confirmed |
- Yes tests should always be executed on a clean Joomla.
- It is reccomended to run the installation test first, that's what we do with drone. But actually you can also run it in between.
- You have to set as secret
tEstValuein the configuration.php, because the tokens for authentication are built with the secret. The installation test does that already for us.
So the instructions were indeed missing vital information - I will do an update
| Status | Confirmed | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-04-18 13:10:58 |
| Closed_By | ⇒ | brianteeman |
On some point we have to migrate them to the manual, just didn't had time yet. I made that document basically for the GsoC students.
Regarding 3. I think you have to provide an API token in the settings of the super user. That could be already part of the regular backend documentation or elsewhere.