Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
14 measurements spanning 42 days, net -56. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 6,874–6,946 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Sept 2026, 18:41
6,882
-5
14 Sept 2026, 19:55
6,887
-5
11 Sept 2026, 16:21
6,892
-3
7 Sept 2026, 01:40
6,895
+1
2 Sept 2026, 07:02
6,894
-2
30 Aug 2026, 03:45
6,896
-6
27 Aug 2026, 02:43
6,902
-5
24 Aug 2026, 07:33
6,907
-4
20 Aug 2026, 10:22
6,911
-6
17 Aug 2026, 17:16
6,917
-3
14 Aug 2026, 16:24
6,920
-9
11 Aug 2026, 00:26
6,929
-7
8 Aug 2026, 05:46
6,936
-2
7 Aug 2026, 10:17
6,938
first reading
Engagement
27 posts held, back to 23 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 12 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 27 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
1,137 reactions across 27 posts, in 10 distinct kinds. The most used accounts for 77.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
882
77.6%
👍
131
11.5%
❤
73
6.42%
👌
38
3.34%
💯
5
0.44%
🤣
2
0.176%
🤪
2
0.176%
🦄
2
0.176%
👏
1
0.088%
🥰
1
0.088%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 27 of the 27 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1,137 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 23 June 2026 to 19 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
Stars received
13
across the posts below
Posts paid on
2
of 27 we hold a reading for · 7%
Most on one post
7
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @qa_road_channel. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 27 most recent posts we hold for this entry, published 23 June 2026 to 19 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Advertising
Ad load
3.70%
1 of 27 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
2,370
over 1 measured post
Median views · rest
2,390
over 26 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2W5zFHoXy7w
1
29 June 2026
29 June 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 27 most recent posts we hold, published 23 June 2026 to 19 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Кстати, забыл рассказать 🙂
Недавно прошёл курс по интеграциям и проектированию API для системных аналитиков.
Эта тема, мне особенно близка, учитывая мою специализацию на бэке и интеграциях.
А какие курсы вы недавно прошли или проходите сейчас?
Работаем в консоли на удаленном сервере
БД в Docker
Давайте устроим сегодня созвон в 21 по мск
Ссылка на созвон https://meet.jit.si/IntensePrisonsCruiseIndeed
надо оживать)
Как работают access и refresh токены 🔔
После логина сервер должен узнавать пользователя при каждом запросе, не спрашивая пароль заново. Токен - временное удостоверение вместо пароля. Проблема в том, что его можно украсть, и чем дольше он живёт, тем опаснее кража.
Разберём по шагам весь путь токенов, и почему их два, а не один
📌 Шаг 1: логин
Сервер проверяет логин и пароль и выдаёт сразу два токена - короткоживущ…
🚀 Вопрос «Куда расти из мануального тестирования и как начать автотесты на Java?» всё ещё актуален.
Поэтому хочу лично от себя порекомендовать новый курс Java QA Automation 2026 от Олега Пендрака автора канала @thread_qa_blog, который проводил у нас мастер-классы и предоставил свою песочницу для нашего бесплатного курса по авто на питоне для UI автотестов.
📌 Курс работает с полным набором технологий, которые реаль…
JWT: что внутри токена 🧐 (Очень важная тема)
JWT обычный текст в кодировке Base64URL, это не шифрование. Любой может декодировать токен и прочитать, что внутри - защищена только подпись, а не содержимое. Токен состоит из трёх частей через точку: header.payload.signature.
👀 Где используется и почему
HTTP - протокол без памяти: каждый запрос сервер видит "с нуля". JWT решает это без хранения состояния сессии на се…
🎯 ИИ заменит тех, кто не умеет с ним работать
Под прошлым постом было много опасений про ИИ и наше QA будущее. Думаю страх обоснован наполовину. 🧐
Сейчас я работаю как системный аналитик по внедрению ИИ в бизнес-процессы и тестировщик.
Из моего опыта могу сказать, что в QA очень много контекста "под капотом". Той самой работы, которая скрывается за формальной постановкой задач и последующим уточнением данных.
📌 …
🌿 Пост для всех, кому непросто
Просто несколько мыслей.
📌 Тем, кто ищет работу
Поиск работы в тестировании сейчас может занимать месяцы, но это не значит, что с тобой, что-то не так. Рынок сложнее, чем раньше, конкуренция выше.
Отказ - не всегда оценка твоих навыков. Обычно это просто "не сошлось" по причинам, которые от тебя не зависят. И таких причин десятки.
📌 Тем, кому тяжело на текущей работе
Выгорание, …
🔥 Хочешь научиться тестировать ИИ системы?
Приходи на Курс «Тестирование и оценка AI»
Научишься:
📌 Тестировать ML/DL, LLM, RAG, AI-агентов
📌 Строить процесс оценки ИИ
📌 Работать с DeepEval, Promptfoo, Ragas, LangFuse и др.
📌 Создавать тестовые данные для тестирования
📌 Искать уязвимости в ИИ системах
40+ часов практики на реальных ИИ-системах
Автор: Александр Мешков, Head of AI Evaluation, автор фреймворка для оце…
🔥 Query-параметры и path-параметры в URL. В чём разница
Оба способа передают данные через URL, но решают разные задачи.
📌 Path-параметр это часть адреса
Указывает на конкретный ресурс, обычно ID. Без него URL не имеет смысла.
GET /api/orders/125
125 это path-параметр, обязателен для работы эндпоинта.
📌 Query-параметр это уточнение к запросу
Идёт после ?, пары ключ=значение через &. Обычно необязателен - для фи…
HTTP-заголовки в запросах
Заголовки - это метаданные запроса и ответа. Они не про "что передаём", а про "как передаём" и "кто ты такой".
🔴 Группы заголовков
• Содержимое - Content-Type, Content-Length
• Авторизация - Authorization
• Состояние клиента - Cookie (запрос), Set-Cookie (ответ)
• Кэширование - Cache-Control, ETag
• О клиенте - User-Agent, Accept
• Кастомные - X-Request-ID, X-Client-Version
📌 Content-T…
🔥 Идентификация, аутентификация, авторизация. В чём разница
Эти три термина часто путают, хотя они решают разные задачи и идут строго друг за другом.
👀 Простая аналогия - вход в офис
Идентификация - ты называешь своё имя на входе: «Я Котов Мурмур»
Аутентификация - охранник проверяет пропуск и сверяет фото: «Действительно ли ты Котов Мурмур?»
Авторизация - пропуск открывает дверь только на 3 этаж: «Тебе разрешен…
@ProTestingInfo - Канал Надежды Дудник, автора на Хабре, ментор QA и эксперта в тестировании ПО. Здесь одинаково комфортно и тем, кто только гуглит «STLC», и крепким QA-спецам.
Что внутри для твоей карьеры:
• 📂 База шаблонов: забирай в файлах готовые чек-листы, тест-кейсы, тест-планы и отчеты.
• 🧠 Интерактив: квизы на знание теории, которые заменяют скучное чтение большого потока информации.
• 🛠 Hard Skills: разбо…
🔥14👍4❤3👌2🤪2🤣1
Showing the 12 most recent of 27 posts we hold for @qa_road_channel. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Posts edited after publishing
@qa_road_channel edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
12 August 2026
Most recent edit
12 August 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 9 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
QA Sklad - Склад тестировщика @qa_sklad · 23,347 Telegram ranks this channel #30 of 94 here — alongside 93 others — read 18 September 2026
Artsiom Rusau QA Life - Тестировщик с нуля @qachanell · 30,246 Telegram ranks this channel #41 of 92 here — alongside 91 others — read 7 September 2026
Серьезный тестировщик 🐞 @serious_tester · 30,126 Telegram ranks this channel #68 of 92 here — alongside 91 others — read 7 September 2026
Тестировщик от бога @godoftesting · 29,550 Telegram ranks this channel #75 of 90 here — alongside 89 others — read 8 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“QA_Road_channel” (@qa_road_channel), 6,882 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/qa_road_channel.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.