Telegram RegisterThe public register of Telegram

Channel

📚 ProTestingInfo 🔷 Канал по тестированию 📚

@protestinginfo

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

14,872subscribers

-6 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001472805556
TypeChannel
Username@protestinginfo
Description📌Информация для начинающих и для коллег в области QA, для личного закрепления знаний. 📌Теория, тесты, практика Ментор-Консультация - 6 тр/час Курс @info_course_protestinginfo https://protestinginfo.ru Вопросы @nadin_qa ИП РКН: https://clck.ru/3FWD9v
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/protestinginfo

Growth

14,87214,87814,8757 August 2026 — 14,878 subscribers7 August 2026 — 14,878 subscribers7 August 2026 — 14,873 subscribers8 August 2026 — 14,875 subscribers9 August 2026 — 14,877 subscribers10 August 2026 — 14,876 subscribers11 August 2026 — 14,874 subscribers13 August 2026 — 14,872 subscribers7 August 202613 August 2026
8 measurements spanning 6 days, net -6. 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 14,871–14,879 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:4514,872-2
11 Aug 2026, 23:5314,874-2
10 Aug 2026, 23:1614,876-1
9 Aug 2026, 20:3814,877+2
8 Aug 2026, 20:2414,875+2
7 Aug 2026, 21:0414,873-5
7 Aug 2026, 05:3014,878no change
7 Aug 2026, 05:2714,878first reading

Engagement

17 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.66%
avg views ÷ 14,872 subscribers
Avg views / post
990
17 posts measured
Reaction rate
1.72%
reactions ÷ views · ER floor
Posts in window
17
of 17 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held17 (31 July 202612 August 2026)
Views total16,828
Reactions total289
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 16:11 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
1,620
Videos
216
Links
1,300

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
8s
Average length
8s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

289 reactions across 17 posts, in 17 distinct kinds. The most used accounts for 21.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉6221.5%
6121.1%
🔥4816.6%
👍4114.2%
227.61%
❤‍🔥206.92%
custom 528972275587116290082.77%
👨‍💻62.08%
41.38%
💯31.04%
🙏31.04%
🏆20.692%
👏20.692%
😇20.692%
😎20.692%
🤗20.692%
💊10.346%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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 17 of the 17 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 289reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 31 July 2026 to 12 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.

Recent posts

12 Aug 2026, 17:58 UTC654 views7 reactionsread 13 August 2026
Photo

ТЕСТИРУЕМ SSE В POSTMAN С GEMINI API👇 Знали ли вы, что в Postman можно тестировать Server-Sent Events (SSE)? SSE — это технология, позволяющая серверу отправлять данные клиенту через одно постоянное HTTP-соединение. В отличие от WebSocket, SSE работает поверх обычного HTTP и автоматически переподключается при обрыве. Идеально для чатов и потоковой генерации AI! ПОШАГОВАЯ ИНСТРУКЦИЯ: 1️⃣ Получаем API ключ: → aistu

3👍3❤‍🔥1

11 Aug 2026, 05:53 UTC912 views24 reactionsread 13 August 2026
Photo

Следующие посты будут про MCP и SDD. Общие определения. подписаться на нельзяграм Сохраняй roadmap 👇 Промпт-инжиниринг + RAG Документацию проекта векторизуют и кладут в RAG. ИИ знает ТВОЙ проект, а не общий интернет. Умеешь: ✓ Писать промпты для генерации тестов ✓ Получать ответы по специфике проекта ✓ Анализировать баги через ИИ-ассистента 🎯 Fullstack QA — 6 областей: 🔌 API (REST, GraphQL, gRPC, WebSocket) 🖥 UI (

🔥10❤‍🔥732🤗2

10 Aug 2026, 12:28 UTC750 views29 reactionsread 13 August 2026
Forwarded from @qa_road_channelPhoto

🌿 Пост для всех, кому непросто Просто несколько мыслей. 📌 Тем, кто ищет работу Поиск работы в тестировании сейчас может занимать месяцы, но это не значит, что с тобой, что-то не так. Рынок сложнее, чем раньше, конкуренция выше. Отказ - не всегда оценка твоих навыков. Обычно это просто "не сошлось" по причинам, которые от тебя не зависят. И таких причин десятки. 📌 Тем, кому тяжело на текущей работе Выгорание,

🔥24❤‍🔥3🏆2

8 Aug 2026, 14:12 UTC≈1,080 views10 reactionsread 13 August 2026
Poll

Статистика: Сколько верно ответили?

  1. 05%
  2. 18%
  3. 219%
  4. 326%
  5. 429%
  6. 58%
  7. Позже отвечу, пока учусь2%
  8. Воздержусь, посмотрю ответы5%

The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

🎉433

8 Aug 2026, 14:12 UTC958 views8 reactionsread 13 August 2026
Poll

В системе есть онлайн-чат. Нужно, чтобы клиент и сервер могли отправлять сообщения друг другу в любой момент после установления соединения. Что наиболее подходит?

  1. SSE7%
  2. WebSocket77%
  3. Webhook10%
  4. REST GET5%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

❤‍🔥4👏2custom 52897227558711629002

8 Aug 2026, 14:12 UTC901 views9 reactionsread 13 August 2026
Poll

У клиента есть запрос: query { user { id name } } Что является главным преимуществом такого подхода по сравнению с типичным REST API?

  1. GraphQL автоматически ускоряет базу данных9%
  2. Клиент может запросить только необходимые поля70%
  3. GraphQL не использует HTTP5%
  4. GraphQL всегда выполняет запросы асинхронно16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

4💯3😇2

8 Aug 2026, 14:12 UTC837 views10 reactionsread 13 August 2026
Poll

Клиент отправил запрос на сервер и должен получить ответ. Сервер при этом может присылать несколько сообщений в рамках одного вызова. Какой вариант gRPC подходит лучше всего?

  1. Unary5%
  2. Server Streaming55%
  3. Client Streaming24%
  4. Bidirectional Streaming17%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

5👍3🔥2

8 Aug 2026, 14:12 UTC848 views13 reactionsread 13 August 2026
Poll

Какой тип API позволяет серверу самостоятельно отправлять события клиенту через установленное HTTP-соединение?

  1. REST25%
  2. SOAP6%
  3. SSE11%
  4. Webhook59%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

73👨‍💻3

8 Aug 2026, 14:12 UTC849 views9 reactionsread 13 August 2026

Posted without readable text

4👨‍💻3😎2

8 Aug 2026, 05:15 UTC969 views2 reactionsread 13 August 2026

Всем хорошего дня! Сегодня проведу тесты, повторим знания и разберём примерные вопросы, которые задавали моим менти на недавних собеседованиях. Хочу поделиться: недавно закончила курс по амбассадорам в Сбере, а скоро начнётся новое обучение - школа интервьюеров. Сейчас периодически провожу собеседования, поэтому уверена, что новые знания точно пригодятся и в этом направлении 🐱 А как у вас сейчас с подготовкой к собес

2

7 Aug 2026, 04:57 UTC≈1,050 views16 reactionsread 12 August 2026
Photo

С КАКИМИ СУБД ТЫ РЕАЛЬНО РАБОТАЛ? 💾 Личный вопрос на собеседовании, где легко потерять конкретику. Как отвечать структурированно: 1️⃣ НАЗОВИ КОНКРЕТНЫЕ СУБД Не говори “работал с базами данных”. Назови конкретно: • PostgreSQL • MySQL • MS SQL Server • Oracle • MongoDB 2️⃣ ЧТО ИМЕННО ТЫ ДЕЛАЛ Расскажи про конкретные действия: • SELECT-запросы (выборка данных) • Подготовка тестовых данных (INSERT) • Проверка целостн

11👍3🙏2

6 Aug 2026, 13:37 UTC≈1,100 views3 reactionsread 12 August 2026
Photo

Коллеги, добрый день. Хочу поделиться с Отзывами по практическим курсам gRPC API или GraphQL API. Хочу также поблагодарить за доверие, полное прохождение курсов, получение сертификатов и за ваши рекомендации. Желаю вам достичь своих целей. Кто еще не присоединился, предлагаю к нам присоединиться. Готова направить в этой теме. Дополнительно подготовиться к собеседованиям QA. Промокод SKILL900 900 ₽ до 31 августа

👍2🙏1

Showing the 12 most recent of 17 posts we hold for @protestinginfo. 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.

Polls

The 5 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

8 Aug 2026, 14:12 UTCAnonymous Poll133 voters

Статистика: Сколько верно ответили?

  1. 05%
  2. 18%
  3. 219%
  4. 326%
  5. 429%
  6. 58%
  7. Позже отвечу, пока учусь2%
  8. Воздержусь, посмотрю ответы5%

The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

8 Aug 2026, 14:12 UTCAnonymous Quiz220 voters

В системе есть онлайн-чат. Нужно, чтобы клиент и сервер могли отправлять сообщения друг другу в любой момент после установления соединения. Что наиболее подходит?

  1. SSE7%
  2. WebSocket77%
  3. Webhook10%
  4. REST GET5%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

8 Aug 2026, 14:12 UTCAnonymous Quiz307 voters

Какой тип API позволяет серверу самостоятельно отправлять события клиенту через установленное HTTP-соединение?

  1. REST25%
  2. SOAP6%
  3. SSE11%
  4. Webhook59%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

8 Aug 2026, 14:12 UTCAnonymous Quiz199 voters

Клиент отправил запрос на сервер и должен получить ответ. Сервер при этом может присылать несколько сообщений в рамках одного вызова. Какой вариант gRPC подходит лучше всего?

  1. Unary5%
  2. Server Streaming55%
  3. Client Streaming24%
  4. Bidirectional Streaming17%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

8 Aug 2026, 14:12 UTCAnonymous Quiz212 voters

У клиента есть запрос: query { user { id name } } Что является главным преимуществом такого подхода по сравнению с типичным REST API?

  1. GraphQL автоматически ускоряет базу данных9%
  2. Клиент может запросить только необходимые поля70%
  3. GraphQL не использует HTTP5%
  4. GraphQL всегда выполняет запросы асинхронно16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 17 most recent posts we hold, published 31 July 2026 to 12 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 95,001 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 4 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.

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.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“📚 ProTestingInfo 🔷 Канал по тестированию 📚” (@protestinginfo), 14,872 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/protestinginfo.

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.