Telegram RegisterThe public register of Telegram

Channel

QA FAQ

@qQAFAQq

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

1,916subscribers

-3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001574461167
TypeChannel
Username@qQAFAQq
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/qQAFAQq

Growth

1,9161,9191,917.57 August 2026 — 1,919 subscribers7 August 2026 — 1,919 subscribers10 August 2026 — 1,916 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net -3. 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 1,916–1,919 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:331,916-3
7 Aug 2026, 10:311,919no change
7 Aug 2026, 10:181,919first reading

Engagement

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

What this channel posts

Video runtime
37s
Average length
37s

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

367 reactions across 16 posts, in 16 distinct kinds. The most used accounts for 28.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10528.6%
🔥8222.3%
😁7319.9%
👍4111.2%
❤‍🔥154.09%
🥰143.81%
82.18%
🍾71.91%
61.63%
🎄30.817%
👀30.817%
😍30.817%
👎20.545%
😱20.545%
🤮20.545%
🤝10.272%

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

Measured over the 18 most recent posts we hold, published 25 October 2025 to 5 June 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
2
across the posts below
Posts paid on
2
of 16 we hold a reading for · 13%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @qQAFAQq. 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 18 most recent posts we hold for this entry, published 25 October 2025 to 5 June 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.

Recent posts

5 Jun 2026, 11:05 UTC471 views19 reactionsread 7 August 2026
Photo

#мероприятия #PeopleSense Второй день шикарной конференции от людей про людей PeopleSense! Пообщалась с множеством прекрасных людей, пересеклась с замечательным прокрастинатологом всея Руси Максом Дорофеевым 😊 На своём выступлении Макс предложил нам поиграть в его новую игру Душнилы 😅 Игра заставляет задуматься о собственных словах и мотивах, так что, если/когда она выйдет на широкую аудиторию, рекомендую, как инте

14🔥3🥰1😁1

15 Apr 2026, 07:35 UTC≈1,870 views18 reactions1 Starread 7 August 2026
Photo

#опрос #яжменеджер Други, принесла вам долгожданные результаты опроса про соотношение QA-Dev в командах разработки 🥳 Еще раз благодарю всех за участие в опросе и за вашу обратную связь! Буду рада вашим плюсикам и комментариям к статье и да пребудет с нами сила ❤️

👍16👎2

2 Apr 2026, 14:47 UTC≈1,790 views16 reactionsread 7 August 2026

Други, несмотря ни на что, я всё еще тут и переезжать пока что не собираюсь 🙃 А сегодня хочу рассказать вам про новый канал для QA и сочувствующих, который ведет мой друг и соратник Володя Кочегаров, Вова, привет! 👋 Вова трудится на поприще QA уже больше 15 лет и сейчас возглавляет QA в компании Атол, с сервисами которой наверняка сталкивались многие из вас 😉 Канал появился сразу и в телеграме и в MAX, чтобы всем б

👍113🤮2

13 Feb 2026, 16:27 UTC≈1,670 views31 reactionsread 7 August 2026
Video

Други, пока я всё ещё обрабатываю многочисленные результаты опроса, в эфире наша постоянная рубрика #мемопауза Не баг, а фича в новом исполнении 💪

😁292

27 Jan 2026, 09:11 UTC≈2,220 views38 reactionsread 7 August 2026
Photo

В продолжение темы мануалов vs автоматизаторов наткнулась тут на очень показательную вакансию 😅🙈

😁32🔥6

22 Jan 2026, 15:01 UTC≈2,140 views7 reactionsread 7 August 2026

#опрос Други, в продолжение интервью с Алиной про образ современного тестировщика, у меня вышла занимательная дискуссия с коллегами на тему соотношения QA-Dev в командах разработки и я решила спросить, а как у вас? С вас - заполнение небольшой анкеты - не больше 1-2 минут вашего времени. Чем больше людей откликнется, тем данные будут богаче! С меня - собрать информацию и написать пост с результатами и моими вывода

6🤝1

20 Jan 2026, 08:20 UTC≈1,630 views26 reactions1 Starread 7 August 2026
Forwarded from @go_to_productionPhoto

Тестирование в 2026: Manual VS Auto Некоторое время назад мы с Олей Артемьевой из «Тестирование и жизнь» сделали статью о том, нужно ли тестировщику уметь автоматизировать в 2026. Короткий ответ: нет. Этот пост — продолжение темы «Manual VS Auto», но с противоположной точкой зрения. В рамках рубрики #интервьюшная поговорили с Олей Ермолаевой — QA Head в Lamoda, автором канала «QA FAQ». Оля — нанимающий менеджер и

🔥21👍5

20 Jan 2026, 08:20 UTC≈1,010 views7 reactionsread 7 August 2026

Други, мы с Алиной Илюхиной, автором канала Багов бояться - в прод не ходить обсудили последние тенденции профессии QA инженера. Будет полезно тем, кто определяется кем быть, когда вырасту с профессией или дальнейшим направлением развития.

4🔥3

12 Jan 2026, 21:22 UTC≈1,270 views18 reactionsread 7 August 2026
Photo

С началом рабочего года! И не будьте как креветочки 😜

🥰12😁51

31 Dec 2025, 14:20 UTC≈1,590 views56 reactionsread 7 August 2026
Photo

Други, вот и заканчивается этот год, как водится, он был непростым и богатым на события 😏 Давайте рефлексировать, вспоминать значимые или просто интересные события и подводить итоги года. Поехали! 🚀 1. Впервые в жизни меня сократили. Из Спортмастера я уходить не планировала, но жизнь решила за меня Спустя время хочу сказать жизни спасибо за этот толчок, потому что моя текущая работа в Ламоде нравится мне ещё больше

368🍾7🎄3🔥2

15 Dec 2025, 14:42 UTC≈1,320 views17 reactionsread 7 August 2026
Photo

Други, до конца года осталось совсем немного и скоро наступит ежегодная рубрика подведения итогов, готовьтесь! 😎 А пока что рада вам представить запись моего доклада с недавнего тимлидского митапа: 📺 Как удобрять инженера, чтобы вырос крепкий лид Я там получилась местами зелёная, но не переживайте, это лечится и уже всё хорошо 😅

10🔥7

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 955,705 of 1,151,006entries 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 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.

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

“QA FAQ” (@qQAFAQq), 1,916 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/qQAFAQq.

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.