Telegram RegisterThe public register of Telegram
Telegram profile photo for QA Live 🚩 Тестирование ПО

Channel

QA Live 🚩 Тестирование ПО

@qa_Iive

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

3,349subscribers

-279 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001603131006
TypeChannel
Username@qa_Iive
CreatedBetween 1 November 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/qa_Iive

Growth

3,3493,6283,488.57 August 2026 — 3,628 subscribers7 August 2026 — 3,623 subscribers10 August 2026 — 3,584 subscribers14 August 2026 — 3,543 subscribers17 August 2026 — 3,489 subscribers20 August 2026 — 3,450 subscribers24 August 2026 — 3,393 subscribers26 August 2026 — 3,358 subscribers30 August 2026 — 3,360 subscribers2 September 2026 — 3,356 subscribers6 September 2026 — 3,349 subscribers7 August 20266 September 2026
11 measurements spanning 31 days, net -279. 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 3,307–3,670 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 17:153,349-7
2 Sept 2026, 14:233,356-4
30 Aug 2026, 06:463,360+2
26 Aug 2026, 22:243,358-35
24 Aug 2026, 00:573,393-57
20 Aug 2026, 08:283,450-39
17 Aug 2026, 18:133,489-54
14 Aug 2026, 05:173,543-41
10 Aug 2026, 23:163,584-39
7 Aug 2026, 14:073,623-5
7 Aug 2026, 04:463,628first reading

Engagement

20 posts held, back to 3 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 20 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 54s
Average length
29s

Measured directly from 4 videos 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

218 reactions across 20 posts, in 11 distinct kinds. The most used accounts for 43.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁9443.1%
👍3917.9%
2812.8%
🤡2411.0%
🔥167.34%
🗿62.75%
💩41.83%
👌31.38%
💔20.917%
👎10.459%
🦄10.459%

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

Measured over the 20 most recent posts we hold, published 3 March 2026 to 20 July 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

20 Jul 2026, 04:15 UTC524 views5 reactionsread 7 August 2026
Photo

🟢Подборка полезностей для тестировщиков 🐞 20 июля 💡 Теория ▫️7 ошибок в оценке QA-задач, из-за которых команда срывает сроки релиза ▫️Мобильный маркетинг начинается с QA: как тестирование влияет на модерацию и рейтинг приложения ▫️Как работать со сложной обратной связью: техники и система обработки ▫️Технический долг в разработке ПО: как QA помогает управлять стоимостью изменений ▫️Заранее находим, что тестировать:

👍5

2 Jul 2026, 10:02 UTC651 views5 reactionsread 7 August 2026
Photo

Claude Code за месяц стал мощнее. Большинство использует его на 10% Как превратить Claude Code не в помощника для кода, а в автономного агента? Чтобы он сам анализировал проект, писал код, запускал тесты, исправлял ошибки и одновременно вел до 15 задач. То, с чем обычно справляется целая команда разработки. CEO университета Зерокодер Кирилл Пшинник проводит открытый практикум. Собираем вживую: – 15 агентов одновре

👍5

2 Jul 2026, 06:21 UTC≈2,390 views8 reactionsread 7 August 2026
Photo

🟢Подборка полезностей для тестировщиков 🐞 Июнь 💡 Теория ▫️Руководство по имитаторам для тестировщиков ▫️Бюджетное тестирование облачных приложений: Testcontainers и LocalStack ▫️Какие задачи в тестировании пора отдать ИИ, чтобы получить результат, а не новые проблемы ▫️От вебинаров до биллинга: что нужно тестировать в EdTech ▫️6 ошибок в метриках дефектов, из-за которых QA теряет контроль над качеством ▫️Аудит нагру

8

11 Jun 2026, 08:38 UTC777 views13 reactionsread 7 August 2026
Photo

Photo, posted without a caption

👍7💩4🤡2

5 Jun 2026, 09:36 UTC925 views7 reactionsread 7 August 2026
Photo

🔥 Открытый практикум по Claude Code без теории Ты слышал, что Claude Code — один из лучших инструментов вайб-кодинга в мире. Зашёл попробовать — а там оплата картой, которая из России не проходит. Ограничения, виртуалки, чужие аккаунты, и фоновый страх, что завтра всё отвалится. CEO университета Зерокодер, Кирилл Пшинник, проведет открытый практикум. Что вы узнаете: — Доступ к Claude Code из России — как установит

🗿6👎1

1 Jun 2026, 05:31 UTC≈2,730 views4 reactionsread 7 August 2026
Video

🟢Подборка полезностей для тестировщиков 🐞 31 мая 💡 Теория ▫️Новости тестирования за февраль-май 2026 ▫️Как оценивать ИИ‑агентов в проде: нижняя планка, трассы и кодовые проверки ▫️Peer testing на основе Закона Линуса ▫️Испытание временем — как тестировать цифровой двойник, если физического объекта ещё не существует ▫️Вы неправильно тестируете асинхронный код: тест проходит раньше, чем выполняется проверка ▫️Не прост

👍4

18 May 2026, 09:18 UTC≈2,900 views9 reactionsread 7 August 2026
Photo

🟢Подборка полезностей для тестировщиков 🐞 18 мая 💡 Теория ▫️GPT-шорткаты: что работает, а что нет ▫️Ты QA и у тебя баги. Какие из них блокируют релиз? ▫️Разбираемся в многообразии видов тестирования ▫️Почему классический подход к QA больше не работает (и виновата ли в этом эпоха ИИ) ▫️Как приручить сервисы-моки ▫️Apache Kafka: как настроить тестирование сообщений в топиках ▫️В агентскую эпоху не все архитектуры кода

9

12 May 2026, 09:01 UTC≈1,020 views23 reactionsread 7 August 2026
Photo

Ручное тестирование - ВСЁ Ручных тестировщиков не зовут на собесы и платят ветку Все из-за кризиса и огромного количества ручников Пора переходить в автоматизацию тестирования! Там легче найти работу и зарплаты выше в ~2 раза В этом тебе поможет канал Димы. Там Senior AQA делится личным опытом переката и рассказывает истории из жизни автотестера Как перейти в AQA из ручного тестирования? Что спрашивают на собесах

🤡22🦄1

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

Forward network

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 1 registered channel — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

Тестировщик от бога
@godoftesting · 29,604
Telegram ranks this channel #27 of 90 here — alongside 89 others — read 8 September 2026
Серьезный тестировщик 🐞
@serious_tester · 30,213
Telegram ranks this channel #40 of 92 here — alongside 91 others — read 7 September 2026
Artsiom Rusau QA Life - Тестировщик с нуля
@qachanell · 30,260
Telegram ranks this channel #72 of 92 here — alongside 91 others — read 7 September 2026

This channel appears in 3 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“QA Live 🚩 Тестирование ПО” (@qa_Iive), 3,349 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/qa_Iive.

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.