Telegram RegisterThe public register of Telegram
Telegram profile photo for Протестировал

Channel

Протестировал

@sqaunderhood

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

1,882subscribers

-5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001143811195
TypeChannel
Username@sqaunderhood
Created22 July 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held11
Confirmed unchanged2 times, most recently 18 September 2026
On Telegramt.me/sqaunderhood

Topic

Technology — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

1,8791,8881,883.56 August 2026 — 1,887 subscribers6 August 2026 — 1,887 subscribers12 August 2026 — 1,888 subscribers17 August 2026 — 1,887 subscribers21 August 2026 — 1,886 subscribers24 August 2026 — 1,887 subscribers27 August 2026 — 1,884 subscribers30 August 2026 — 1,883 subscribers6 September 2026 — 1,879 subscribers11 September 2026 — 1,881 subscribers14 September 2026 — 1,882 subscribers1,8826 August 202614 September 2026
11 measurements spanning 39 days, net -5. 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,878–1,889 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 15:011,882+1
11 Sept 2026, 07:171,881+2
6 Sept 2026, 04:381,879-4
30 Aug 2026, 10:561,883-1
27 Aug 2026, 15:381,884-3
24 Aug 2026, 23:191,887+1
21 Aug 2026, 07:251,886-1
17 Aug 2026, 23:431,887-1
12 Aug 2026, 02:321,888+1
6 Aug 2026, 11:311,887no change
6 Aug 2026, 09:461,887first reading

Engagement

19 posts held, back to 18 December 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 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 19 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

358 reactions across 19 posts, in 24 distinct kinds. The most used accounts for 20.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7420.7%
🤮4612.8%
3910.9%
👍3910.9%
🤡339.22%
💩308.38%
👀154.19%
😭133.63%
😢102.79%
👏92.51%
👎71.96%
❤‍🔥51.40%
🖕51.40%
🤔51.40%
🤣51.40%
🤯51.40%
41.12%
🕊41.12%
🙈41.12%
😨20.559%
4 further kinds41.12%

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

Measured over the 19 most recent posts we hold, published 18 December 2025 to 9 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.

Telegram Stars

Stars received
6
across the posts below
Posts paid on
2
of 19 we hold a reading for · 11%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sqaunderhood. 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 19 most recent posts we hold for this entry, published 18 December 2025 to 9 July 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

9 Jul 2026, 17:14 UTC537 views6 reactionsread 7 August 2026

A collaborative bibliography of papers related to property-based testing https://github.com/ngernest/pbt-bibliography

6

7 Jul 2026, 15:06 UTC721 views10 reactionsread 7 August 2026
Photo

В Github UI появился автоматический дедупликатор тикетов, во время создания нового тикета, но ищет похожие по описанию. Впрочем работает пока так себе, в моём случае это был не дупликат.

🔥6👍31

13 Jun 2026, 06:30 UTC≈1,090 views4 reactionsread 7 August 2026

CirrusCI всё: Cirrus CI will shut down effective Monday, June 1, 2026. Перейдут под крыло OpenAI. В прощальном тексте основатель перечисляет инновации: Over the last nine years, we were fortunate to innovate across continuous integration, build tools, and virtualization. In 2018, we introduced what we believe was the first SaaS CI/CD system to support Linux, Windows, and macOS while allowing teams to bring their own

😢31

4 Jun 2026, 07:23 UTC≈1,090 views10 reactionsread 7 August 2026

Интересная статья про использование сравнительного тестирования для приложений с состоянием - "Vive la Différence: Practical Diff Testing of Stateful Applications". При обновлении stateful-приложений работающих с БД часто возникают трудноуловимые ошибки и традиционные методы (канареечные релизы, роллинг-обновления, cине-зелёное развёртывание) плохо эти ошибки выявляют из-за разделяемого состояния. Стандартные тесты

👍5🔥4🤝1

23 Apr 2026, 11:05 UTC≈1,280 views6 reactionsread 7 August 2026

Раньше ведь как было: изучаешь теорию языков программирования и формальные методы, формальные грамматики, лексический и синтаксический анализ, работу c AST (обход дерева, трансформация), атрибутные грамматики и синтезируемые/наследуемые атрибуты, изучаешь системы типов, семантику программ, чтобы понимать, что означает программа, изучаешь межпроцедурный анализ. Изучаешь алгоритмы статического анализа: анализ потоков д

🤯5👍1

19 Mar 2026, 17:01 UTC≈1,280 views9 reactionsread 7 August 2026
Photo

Sashiko мониторит список рассылки с патчами в ядро Linux (LKML) и запускает ревью этих патчей с помощью LLM (сейчас, как я понял, это Gemini). Результаты публикует в симпатичном WebUI. https://sashiko.dev/

4👀2😨21

13 Mar 2026, 10:45 UTC≈1,600 views12 reactionsread 7 August 2026
File

Если вы хотели погрузиться в тему SDLC, то вот вам знак свыше: в весеннем семестре в ВМК МГУ проходит спецкурс по РБПО. Лабораторные работы будут доступны только студентам, лекции будут транслироваться в Jitsi по ссылке, прослушивание доступно всем желающим просто по ссылке, записи лекций (кроме первой) обещают выкладывать. Лекторы из ИСП РАН и индустрии. 3 марта Вводная лекция. 10 марта Неопределенное поведение и

❤‍🔥54🔥3

12 Mar 2026, 13:16 UTC≈1,410 views19 reactionsread 7 August 2026

5 марта умер сэр Тони Хоар Некролог: https://blog.computationalcomplexity.org/2026/03/tony-hoare-1934-2026.html

😭13🕊4👌1🙏1

4 Mar 2026, 16:48 UTC≈1,700 views10 reactionsread 7 August 2026

Поиск точек разладки (changepoint) это популярная задача в разных областях. Это канал про тестирование ПО, поэтому ограничимся поиском точек разладки при анализе результатов тестирования производительности. В отличие от функционального тестирования результаты тестов производительности нужно постоянно анализировать и выявлять причины отклонений результатов, в некоторых компаниях этим занимаются отдельные команды (Андр

5👍5

2 Mar 2026, 17:24 UTC≈1,230 views21 reactionsread 7 August 2026

После анонса задачи про верификацию оптимизаций в LuaJIT в лаборатории Tarantool мне написал студент Физтеха Алексей и сказал, что хочет взять эту задачу в качестве дипломной работы и с сентября прошлого года мы продолжаем делать верификатор для LuaJIT. Много успели сделать и есть результаты, которыми можно поделиться. Напомню основную идею - научиться моделировать семантику LuaJIT IR с помощью SMT-LIB, декларативно

🔥19👍2

25 Feb 2026, 16:20 UTC≈1,130 views16 reactionsread 7 August 2026

Обычно для оценки степени покрытия кода фаззинг-тестированием используют покрытие по строкам/функциями и редко по ветвлениям. Метрика покрытия MC/DC редко используется для оценка покрытия регресионными тестами вообще и фаззинга в частности, хотя она позволяет получить доказательство того, что логика надежно тестируется в коде. Я сделал патч, чтобы можно было для кода PUC Rio Lua и LuaJIT собирать MC/DC покрытие, мне

🔥11🤔41

19 Feb 2026, 13:39 UTC≈1,240 views6 reactionsread 7 August 2026

In this work, we address this issue by proposing an efficient white-box checker, Emme. Our key idea is to use information that is easily provided by database systems to efficiently check the isolation level of a given transaction history. We present version certificate recovery, a method of recovering the version order and each operation’s version from the database system under test. For efficiency, we also propose t

👍6

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

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

“Протестировал” (@sqaunderhood), 1,882 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/sqaunderhood.

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.