# Page Not Found

The URL `files/5gg2ZV6CickJ84GdvbDW` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Тестирование push-уведомлений](https://vladislaveremeev.gitbook.io/qa_bible/mobilnoe-testirovanie/testirovanie-push-uvedomlenii.md)
- [Основные различия Android/iOS](https://vladislaveremeev.gitbook.io/qa_bible/mobilnoe-testirovanie/osnovnye-razlichiya-android-ios.md)
- [Где искать работу?](https://vladislaveremeev.gitbook.io/qa_bible/faq-dlya-novichkov/gde-iskat-rabotu.md)
- [Тестирование дип линков (mobile deep links)](https://vladislaveremeev.gitbook.io/qa_bible/mobilnoe-testirovanie/testirovanie-dip-linkov-mobile-deep-links.md)
- [Vibe Coding](https://vladislaveremeev.gitbook.io/qa_bible/ai-v-testirovanii/vibe-coding.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://vladislaveremeev.gitbook.io/qa_bible/mobilnoe-testirovanie/testirovanie-push-uvedomlenii.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.

### Option 2 — Browse the documentation index

Full index: https://vladislaveremeev.gitbook.io/qa_bible/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://vladislaveremeev.gitbook.io/qa_bible/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/qa_bible/mobilnoe-testirovanie/testirovanie-push-uvedomlenii.md`).

You may also use `Accept: text/markdown` header for content negotiation.