# Chrome Developer Tools

## Materiały od autorów

* [Strona domowa projektu](https://developers.google.com/web/tools/chrome-devtools/)

## Materiały

* [A list of cool Chrome DevTools Tips and Trick](https://flaviocopes.com/chrome-devtools-tips/)
* [Lista interaktywnych zadań do wykonania](https://testersplayground.herokuapp.com/) 🕹️
* [Aktualizowana lista z poradami odnośnie Chrome Dev Tools](https://umaar.com/dev-tips/)
* [How to Use Chrome DevTools to Test Your Website](https://www.a2hosting.com/blog/chrome-devtools/)
* [How to utilize Chrome Dev tools for QA(manual or automation)](https://sqa.stackexchange.com/questions/33139/how-to-utilize-chrome-dev-tools-for-qamanual-or-automation)
* [Google Chrome Developer Tools Crash Course](https://www.youtube.com/watch?v=x4q86IjJFag) 📺
* [Pro Chrome DevTools Courses](https://egghead.io/browse/tools/chrome-devtools) 📺🕹️💵
* [Kurs Explore and Master Chrome DevTools](http://discover-devtools.codeschool.com/) 📺🕹️💵
* [Chrome DevTools 101: Debugging JavaScript](https://www.youtube.com/watch?v=H0XScE08hy8) 📺
* [Using The Chrome Developer Tools](https://www.pluralsight.com/courses/chrome-developer-tools) 📺💵
* <https://www.linkedin.com/learning/learning-chrome-web-developer-tools-2/>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ksiazka.testowanieoprogramowania.pl/narzedzia/chrome-developer-tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
