Video, posted without a caption
😁9

Channel
@Pro_Test_studio
On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
1,068subscribers
-7 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001821302123 |
|---|---|
| Type | Channel |
| Username | @Pro_Test_studio |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/Pro_Test_studio |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 16:40 | 1,068 | -1 |
| 30 Aug 2026, 01:03 | 1,069 | +1 |
| 26 Aug 2026, 19:04 | 1,068 | -1 |
| 17 Aug 2026, 22:34 | 1,069 | +1 |
| 14 Aug 2026, 21:43 | 1,068 | -5 |
| 11 Aug 2026, 04:41 | 1,073 | -2 |
| 8 Aug 2026, 11:32 | 1,075 | no change |
| 8 Aug 2026, 01:32 | 1,075 | first reading |
20 posts held, back to 27 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 September 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 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.
211 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 27.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 58 | 27.5% | |
| 😁 | 48 | 22.7% | |
| 👍 | 38 | 18.0% | |
| 🤣 | 37 | 17.5% | |
| ❤ | 20 | 9.48% | |
| 💯 | 5 | 2.37% | |
| 🌚 | 2 | 0.948% | |
| 🎉 | 2 | 0.948% | |
| 😍 | 1 | 0.474% |
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 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 211 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 27 August 2025 to 20 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
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.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| empotencyKey | 1 | 10 September 2025 | 10 September 2025 |
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 27 August 2025 to 20 September 2025. 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.
Video, posted without a caption
😁9
🤔 Загадочные символы в отчете Тестируем экспорт отчёта в CSV. В файле вместо кириллических букв: СпиÑок клиентов ❓ В чём настоящая проблема? Отмечайте правильный эмодзи ❤️🤩🌚🔥
🔥19
А что, так можно было? 👀 if (day == Wednesday) { print(“Маленькая пятница 🎉”); }
🔥7😁7🤣6👍1
🤷♂️ Как воспроизвести «невоспроизводимый» баг через HAR-логи Один из самых бесящих кейсов: у пользователя баг случается, а у тебя — нет. Решение простое: попроси HAR-лог. 1️⃣ Что такое HAR HAR (HTTP Archive) — это история всех запросов/ответов браузера: заголовки, куки, тело запросов. Можно вытащить прямо из DevTools. 2️⃣ Как выгрузить В Chrome DevTools → Network: — включи галочку Preserve log — повтори шаги, где…
👍6
Выходные — для отдыха, а не для рабочих чатов 😉 Берегите себя и свою психику 💙
😁7🤣6💯3
📌 Инструмент недели: Bug Magnet Минималистичное расширение для браузера, которое экономит массу времени на ручных проверках. Что умеет: ➡️ В один клик подставляет популярные edge-cases в поля ввода (длинные строки, спецсимволы, SQL-инъекции, email с «+» и др.) ➡️ Помогает проверить поведение форм без утомительного копипаста тестовых данных ➡️ Работает прямо из контекстного меню браузера ➡️ Позволяет добавлять свои …
🔥9
Правильный ответ
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
🤔 Задача — API Вы тестируете метод POST /orders, который создаёт заказ. ✔️ Ожидаемый результат при успехе: 201 Created + JSON с данными заказа. При нагрузочном тесте (~300 req/sec) замечаете: ➡️Иногда вместо 201 приходит 409 Conflict. ➡️ В ответе сервера сообщение: "Duplicate order detected". ➡️В логах видно, что повторные запросы с одинаковым orderIdempotencyKey сервер считает дубликатами. Что это означает❓
📹 Вот так примерно выглядит нагрузочное тестирование со стороны 🤣🤣 Напоминаю: среда — это маленькая пятница 🍉✨ Запасаемся настроением, неделя почти позади
🤣10👍3😁3🌚1
🩵Эксклюзивная вакансия ко Дню тестировщика — Senior Bug Hunter! Обязанности: 🩷Ловить баги в коде и в жизни быстрее, чем они успевают воспроизвестись. 🩷Поддерживать стабильность команды даже в режиме продакшн. 🩷Прокачивать скилл «вижу всё» до 99 lvl. Мы предлагаем: 🟣Бесконечный поток интересных кейсов (и только с результатом passed). 🩷Премии в виде кайфа от чистого билда. 🟣Тимлида по имени «Удача» и заказчика под ни…
❤17🔥3🎉2😍1
🐢 Симулируем плохой интернет прямо в терминале Иногда баги вылезают только «на медленном интернете». Но где взять настоящий 3G или убитый Wi-Fi под рукой? 📌 Выручает встроенный инструмент tc — он умеет эмулировать задержки, потери и дублирование пакетов прямо на уровне ОС: sudo tc qdisc add dev lo root netem delay 600ms loss 15% duplicate 5% Что это значит: ➖delay 600ms → каждое соединение тормозит на 0.6 сек ➖l…
👍9🔥6
Какой язык чаще всего вызывает проблемы при тестировании локализации❓
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 20 posts we hold for @Pro_Test_studio. 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.
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Правильный ответ
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Какой язык чаще всего вызывает проблемы при тестировании локализации❓
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Какой реальный объект стал "первым официально задокументированным багом" в истории IT ❓
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🤔
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 27 August 2025 to 20 September 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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 1 seed channel's Telegram-generated recommendation list 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Все про QA | Pro-Test.studio” (@Pro_Test_studio), 1,068 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Pro_Test_studio.
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.