Telegram RegisterThe public register of Telegram
Telegram profile photo for Тестирование | TestGrow

Channel

Тестирование | TestGrow

@QAtestgrow

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

5,296subscribers

-45 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-1001861187747
TypeChannel
Username@QAtestgrow
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/QAtestgrow

Growth

5,2965,3415,318.57 August 2026 — 5,341 subscribers7 August 2026 — 5,341 subscribers10 August 2026 — 5,335 subscribers12 August 2026 — 5,332 subscribers16 August 2026 — 5,328 subscribers19 August 2026 — 5,319 subscribers22 August 2026 — 5,321 subscribers25 August 2026 — 5,307 subscribers28 August 2026 — 5,303 subscribers1 September 2026 — 5,298 subscribers4 September 2026 — 5,296 subscribers7 August 20264 September 2026
11 measurements spanning 28 days, net -45. 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 5,289–5,348 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 09:385,296-2
1 Sept 2026, 03:165,298-5
28 Aug 2026, 23:435,303-4
25 Aug 2026, 20:235,307-14
22 Aug 2026, 20:385,321+2
19 Aug 2026, 01:075,319-9
16 Aug 2026, 08:345,328-4
12 Aug 2026, 23:585,332-3
10 Aug 2026, 10:015,335-6
7 Aug 2026, 14:175,341no change
7 Aug 2026, 14:075,341first reading

Engagement

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

Reaction mix

341 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 64.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥22164.8%
👍9327.3%
😁205.87%
💯51.47%
🥰20.587%

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 341 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 19 February 2026 to 23 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.

Advertising

Ad load
15.0%
3 of 20 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
1,730
over 3 measured posts
Median views · rest
1,790
over 17 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
eridPostsFirst seenLast seen
2VtzqwLBqag120 May 202620 May 2026
2Vtzqwdgfo214 March 20264 March 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 20 most recent posts we hold, published 19 February 2026 to 23 July 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.

Recent posts

23 Jul 2026, 07:44 UTC708 views14 reactionsread 12 August 2026
Photo

Всем привет! У меня отличные новости, я определился с датой старта 4-го потока на курсе по оценке и тестированию ИИ систем! Ииии…. мы начинаем 9 сентября! Если вы давно хотели изучить для себя эту область тестирования, но откладывали, то сейчас до 19 августа вы можете записаться на курс и получить скидку 10% на все обучение. Для записи нужно просто оставить заявку на сайте: eval-ai.com Напомню, что это едиственны

🔥11👍3

2 Jul 2026, 06:02 UTC≈1,150 views7 reactionsread 12 August 2026
Photo

🔥 Как тестировать задачи быстрее, не теряя в качестве Если ты всё ещё: - пишешь чек-листы вручную - не понимаешь, что от тебя хотят в задаче - долго разбираешь ТЗ и требования - не понимаешь, в чём ошибка и как тестировать Показываю, как использовать ИИ в тестировании, чтобы делать рутину быстрее и аккуратнее. Нейросети - это новый инструмент, а не замена тестировщика. ⚡️ Реальный пример: Анализ ТЗ на 30 страниц:

👍7

21 May 2026, 06:01 UTC≈2,150 views23 reactionsread 12 August 2026
Forwarded from @qabigtechPhoto

1 мая я купил себе Claude Code, про него все говорили, и решил: буду использовать его каждый день. Прошёл 21 день. Что из этого получилось? Я не настоящий программист. Но за этот месяц с Claude Code я навайбкодил несколько рабочих тренажёров для QA и AI-скиллы для анализа требований, написания тест-кейсов и разбора баг-репортов. И часть из этого уже реально работает в моем проекте, а что то вы можете потрогать на с

🔥16👍7

21 May 2026, 06:01 UTC≈1,700 views1 reactionsread 12 August 2026

сегодня с Сергеем поговорим про Claude Code, присоединяйтесь, будет интересно!

👍1

20 May 2026, 14:37 UTC≈1,760 views4 reactionsread 12 August 2026
Advertisementerid 2VtzqwLBqagPhoto

Как жить QA в 2026 году? Коллеги из Авито исследуют этот вопрос с научным подходом в своём подкасте «Не воспроизводится». В выпусках они уже разобрали: — чем сегодня QA отличаются от разработчиков; — может ли ИИ полностью заменить тестировщиков; — когда нужна автоматизация, а когда всё-таки удобнее ручные тесты, и многое другое. 🎧 Слушать подкаст: — Яндекс Музыка — YouTube — Любимый стриминг ⚡️ А ещё коллеги пров

🔥4

20 May 2026, 07:56 UTC≈1,590 views8 reactionsread 12 August 2026
Photo

Сегодня я хотел вам напомнить о моей опенсорсной библиотеки по оценке систем на базе ИИ. За последнее время библиотека несколько преобразилась, а именно: • теперь есть поддержка более 50 различных AI провайдеров в качестве оценщика, включая готовую интеграцию для кастомных моделей, ollama self-hosted и MLX моделей • расширилось количество агентских метрик до 9 • подключить свою ИИ систему можно просто как в Postman,

🔥7👍1

30 Mar 2026, 07:39 UTC≈2,100 views9 reactionsread 12 August 2026
Photo

Всем привет! В выходные, после просмотра пары видео на тему развития AI подумал, что сегодня существует большое количество бенчмарков на разные возможности модели, включая кодинг, но почему то нет бенчмарка на оценку моделей и агентов в части генерации тест-кейсов (не unit). Поэтому, я решил попробовать подумать над этой задачей и решить ее. Это не просто проект. Потенциально - это будет полноценный научный проект

🔥9

25 Mar 2026, 07:03 UTC≈2,030 views56 reactionsread 12 August 2026
Photo

Ура, наконец то я это сделал, и опубликовал мою книгу по основам тестирования ПО. Книга получилась достаточно большой, более 500 страниц и включает в себя следующие разделы: • Основы тестирования • Тест-дизайн • Тестирование UI • Тестирование API и брокеров • Основы сетей для тестировщика • Основы работы с БД • Основы Git и Docker Базой для данной книги послужили все мои наработки, сделанные в рамках проекта testgr

🔥44👍12

19 Mar 2026, 09:23 UTC≈2,070 views7 reactionsread 12 August 2026

Всем привет! Если тут кто недавно (в течении полугода) искал работу? Поделитесь в комментариях на какую позицию искали, в какой стране и что по итогу?) Хочется послушать ваше мнение на тему того, что сейчас происходит на рынке труда? Все мои проекты: TG канал по тестированию AI | Курс по оценке и тестированию AI | Курс по тест-менеджменту | Youtube channel | Платформа TestGrow | Практика по тестированию | База зн

😁4👍3

17 Mar 2026, 07:01 UTC≈1,790 views10 reactionsread 12 August 2026
Photo

🔥 90% тестировщиков используют AI неправильно Поэтому тратят часы на задачи, которые можно сделать за минуты. ⚡️ Реальный пример: Анализ ТЗ на 30 страниц раньше 12 часов → с AI 4 часа Обновлённый курс «Тестируем с ИИ» 🚀 Подойдет, если у тебя: — огромные ТЗ — сложные логи — тонна документации — давление по срокам → Эти задачи можно делать в 2-3 раза быстрее Сможешь делать: 📌 Анализировать сложные задачи 📌 Ген

🔥6👍2😁2

16 Mar 2026, 15:51 UTC≈1,460 views23 reactionsread 12 August 2026
Photo

Всем привет! Завтра буду говорить про тестирование ИИ🔥 Как ИИ меняет профессию тестировщика? 17 марта, во вторник, встречаемся в прямом эфире «Просто искать работу сложно». Спикеры: 🗣 Александр Мешков — руководитель практики тестирования и оценки AI в FirstLineSoftware. Создатель eval-ai-library — open-source фреймворка для оценки AI. Разработчик обучающих продуктов для тестировщиков. 🗣 Кира Кузьменко — рекрутер

🔥14👍8🥰1

14 Mar 2026, 08:25 UTC≈1,230 views21 reactionsread 12 August 2026
Photo

Всем привет! Очень нужна ваша помощь и поддержка!! Как возможно вы знаете в последнее время я активно занимаюсь развитием области тестирования ИИ систем и недавно я выпустил новую версию моей библиотеки eval-ai-library 0.5.1. И мне нужна ваша помощь в продвижении моего фреймворка, поэтому я буду благодарен, если вы сможете поставить звезды фреймворку⭐⭐⭐ на GitHub, это поможет сделать мой фреймворк более видимым дл

🔥13👍8

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

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

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.

Artsiom Rusau QA Life - Тестировщик с нуля
@qachanell · 30,260
Telegram ranks this channel #15 of 92 here — alongside 91 others — read 7 September 2026
Тестировщик от бога
@godoftesting · 29,604
Telegram ranks this channel #44 of 90 here — alongside 89 others — read 8 September 2026
Серьезный тестировщик 🐞
@serious_tester · 30,213
Telegram ranks this channel #46 of 92 here — alongside 91 others — read 7 September 2026
IT - стажировки и обучение
@it_interns · 31,282
Telegram ranks this channel #79 of 97 here — alongside 96 others — read 6 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 4 September 2026 — this entry's latest reading, not the date you are reading this.

“Тестирование | TestGrow” (@QAtestgrow), 5,296 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/QAtestgrow.

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.