Try lighthouse CLI to measure the performance of URLs with some extensions on.
With
lighthouse https://www.bing.com/search?q=curse+words --output json --output-path D:\lighthouseResults\0506.json --disable-device-emulation --chrome-flags="--user-agent=edge --window-size=360,640 --enable-experimental-extension-apis"
it doesn't seem that the extension was working(usually takes a few seconds, very slow), and did not find http requests that were suppose to be there in the report.
How should I do it in Lighthouse or I'm looking at the wrong tool?
Related
We use Elastic Search throughout most of our app, and up until today, we've never had issues with testing those features via Cypress. One feature in our app is a calendar tool that populates a list with appointment dates and times. When accessing this calendar tool manually via Chrome, the list correctly populates without issue. When opening this tool during a Cypress spec, and ONLY during a Cypress spec, the results fail to load. The console spits out an error that just says "[useElasticsearch] incorrect header check" with no other information. In checking the network tab, we can confirm that the ES query is performed and returns results successfully, but the page is not updated with those results.
Note that this is NOT the result of a cy.request(), this error occurs through standard UI navigation. This issue, as I mentioned, ONLY occurs when testing via Cypress. Due to this, we are hesitant to make changes to the backend of the app, since it works perfectly fine in all other scenarios. This has been reproduced on Cypress versions 5.1.0, 6.1.0, 7.1.0, and 8.0.0. This has also been reproduced in Cypress when using the Chrome, Electron, and headless browsers.
Has anybody else encountered this issue?
I've just started with Gatsby + Contentful using their "Launch onboarding button" and the starter repo at git clone https://github.com/contentful/starter-gatsby-blog.git. I am familiar with React but not very familiar with GraphQL or Contentful.
When I make an edit to my content at https://app.contentful.com/, I restart my server (npm run dev) in order to query for those changes, but that takes quite a few seconds.
Is there a faster way to redo the GraphQL query during local development, without having to restart my server?
Gatsby exposes an environment variable called ENABLE_GATSBY_REFRESH_ENDPOINT. If it's set to true, it exposes a webhook under /__refresh that can receive POST requests to refresh the sourced content.
So basically, if you change your running command to:
"develop": "ENABLE_GATSBY_REFRESH_ENDPOINT=true gatsby develop",
You can trigger a http://localhost:8000/__refresh locally to refresh your content. Alternatively, for a more automated way you can create a command like:
"refresh": "curl -X POST http://localhost:8000/__refresh"
You can check for further details at https://www.gatsbyjs.com/docs/refreshing-content/
When I run a suite of tests using Cypress, I get a TON of HTTP request logs to the terminal output. I think this image best shows the issue. In it, you can see the command I run to start cypress, and that following it comes a long list of every HTTP request made during the tests.
Is there a way to hide them all?
You can add the following to cypress.json:
"morgan": false,
The logs you see are from express (a built-in server within cypress).
I run my laravel app #localhost.
```php artisan serve --host=localhostIP```
On top I run an Andoid app with the same base URL.
Could anyone tell me how can I debug incoming API´s calls
like if BASEURL/users is called?
Furthermore, how can I log the happening events in the console
I am developing API's with laravel too, i do it this way:
composer require laravel/homestead to have it all in a vm 😉 see https://laravel.com/docs/master/homestead for more information, i use the "per project" installation
Download postman to have the best tool for sending querys to your api and to test your api quick -> https://www.getpostman.com (i use it free)
configure and run your homestead (it's not that complicated).
your homestead is fit with php and xdebug enabled
i am using phpStorm and have my vagrant setup as deployment target
"listen to debug" with phpstorm
to your GET requests, add a queryparam XDEBUG_SESSION_START=PHPSTORM
i can debug my api now 😉
i also wrote https://logcrawler.de to receive the log informations of all my api's and all my server 🤩
I hope, i could help you a little bit
This is my way, but I think it's not good!
Create router api in config/web, Eg:
router/api: Route::post('/check_api', [CheckController::class, 'testFunc'])->name('api.check_api');
web/api: Route::post('test/check_api', [CheckController::class, 'testFunc'])->name('test.check_api');
Create a post by form or ajax in one resource/view like index
Go to page, and debug with phpstorm
You can use logging feature of Laravel. Apply Logs on entry point of application to test whether API url is hitting or not.
use postman
https://www.getpostman.com/downloads/
it's an excellent thing very much usefull
I am making a website using Laravel 5.4 that gets data from an api using guzzlehttp. I am making 96 requests, most of them (around 94) only return a few lines of json. This makes the website very slow to load (55 seconds). Am I doing something wrong?
Probably most of the requests can be done in parallel. Try to use Guzzle's async requests for that.