Channel
@testit_tms
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,575subscribers
-17 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001494347823 |
|---|---|
| Type | Channel |
| Username | @testit_tms |
| Created | Between 1 May 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/testit_tms |
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 17 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 09:59 | 1,575 | -2 |
| 5 Oct 2026, 00:00 | 1,577 | -2 |
| 26 Sept 2026, 02:17 | 1,579 | -5 |
| 17 Sept 2026, 08:21 | 1,584 | -2 |
| 9 Sept 2026, 20:38 | 1,586 | -4 |
| 31 Aug 2026, 19:44 | 1,590 | -1 |
| 28 Aug 2026, 09:24 | 1,591 | +1 |
| 25 Aug 2026, 03:03 | 1,590 | -3 |
| 21 Aug 2026, 19:17 | 1,593 | -1 |
| 18 Aug 2026, 06:42 | 1,594 | +1 |
| 9 Aug 2026, 05:21 | 1,593 | +1 |
| 6 Aug 2026, 07:32 | 1,592 | no change |
| 6 Aug 2026, 02:22 | 1,592 | first reading |
7 posts held, back to 17 July 2026 — the 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 7 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
22 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 11 | 50.0% | |
| ❤ | 6 | 27.3% | |
| 👍 | 3 | 13.6% | |
| custom 5334515231794150495 | 2 | 9.09% |
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 is Telegram’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 6 of the 7 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 26 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 17 July 2026 to 7 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.
MCP* Test IT, автоархивация и новый интерфейс прогонов — разбор ключевых изменений Test IT 5.8 Fornax. Приглашаем узнать, как новая версия меняет подход к работе с ИИ в тестировании и упрощает ежедневные задачи через интеграцию инструментов. 🗓 11 августа в 14:00 (МСК) На вебинаре расскажем, как: ✔️Работать с библиотекой тестов через ИИ-агента без копирования данных; ✔️Актуализировать тестовые сценарии прямо из сре…
Протокол MCP Test IT или API: что выбрать для работы с ИИ? Интегрируете искусственный интеллект в процессы тестирования? Разбираемся, какой инструмент подходит для ваших задач. ⏩Листайте карточки: рассказали про ключевые отличия и сценарии для каждого инструмента. Как MCP Test IT повышает эффективность при работе с ИИ: 🟦Встроенная защита от ошибочных действий; 🟦Готовые сценарии для типовых задач тестирования; 🟦Кон…
🔥3❤1
В последнем релизе представлена Test IT MCP — интеграция с ИИ-ассистентом, которая работает иначе, чем привычные решения. ☑ Суть подхода: ИИ анализирует тестовую модель проекта ➡выявляет проблемы и дубликаты ➡ предлагает конкретный план ➡ выполняет изменения в платформе управления тестированием после вашего подтверждения. В карточках разобрали: ✔ Что это за интеграция и ее отличие от других решений; ✔ Три способа в…
🔥3
Как запускать автотесты в GitLab автоматически: настройка расписания за 2 минуты В новом рецепте рассказали как настроить автоматический запуск тестов в GitLab CI и Test IT по расписанию, чтобы забыть о ручных запусках и пропущенных прогонах. ⏩ Листайте карточки или читайте подробную инструкцию: https://clck.ru/3UqEyz 💬Пишите в комментариях, на какие темы вы бы хотели увидеть рецепты в следующий раз? Тестируйте с…
🔥2
Переходим от тест-кейса к интерфейсному автотесту: быстро и удобно 🔥 Внешний сервис для автоматизации тестирования теперь умеет напрямую импортировать сценарии из вашей библиотеки тестов в Test IT и превращать их в готовые интерфейсные автотесты. Интеграция позволяет использовать накопленную документацию как основу. ИИ-агент самостоятельно анализирует шаги, проходит сценарий в браузере и выдает готовый код. Работае…
🔥3❤2👍2
🚀 ИИ в тестировании: какие сценарии реально работают? Рассказываем, куда движется рынок ИИ-инструментов для тестирования и какие сценарии прямо сейчас дают пользу командам. В статье найдете ответы от Евгения Хафизова: 🟦 что за инструменты в тестировании уже используют ИИ; 🟦 какие задачи команды можно автоматизировать с ИИ; 🟦 чем ИИ-ассистенты отличаются от ИИ-агентов; 🟦 где без контроля инженера пока не обойтись; 🟦…
❤3custom 53345152317941504952👍1
↖️ Какую одну задачу вы готовы доверить ИИ при идеальном ее выполнении? Искусственный интеллект уже помогает командам по оценке качества ПО работать с тест-кейсами, документацией и рутиной. В Test IT тоже есть интеграции с большими языковыми моделями, которые ускоряют работу с тестовой базой. Но рынок движется дальше: на смену ИИ-помощникам приходят автономные агенты, которые могут брать на себя отдельные сценарии…
Showing the 7 most recent of 7 posts we hold for @testit_tms. 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.
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.
Named by 6 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.
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.
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.
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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Test IT TMS” (@testit_tms), 1,575 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/testit_tms.
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.