Одна запись в фикстуре может скрыть сломанный фильтр В примере из документации Pact клиент ищет аллигатора Mary через параметр name. Сервер понимает firstname, а неизвестный параметр молча игнорирует. В тестовых данных только Mary. Сервер возвращает всех аллигаторов, то есть одну Mary. Проверка контракта проходит, хотя фильтр не сработал. Как сделать ошибку заметной — Для provider state подготовьте две записи на с…

Channel
Библиотека тестировщика | QA, тестирование, quality assurance, manual testing, autotesting, ручное тестирование, автотесты
@testerlib
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
8,917subscribers
-171 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001298059592 |
|---|---|
| Type | Channel |
| Username | @testerlib |
| Description | Все самое полезное для тестировщика в одном канале. Наши курсы: https://clc.to/wlBkTA По рекламе: @tproger_sales_bot Учиться у нас: https://proglib.io/w/12538d6f Для обратной связи: @proglibrary_feeedback_bot |
| Created | 29 January 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/testerlib |
Topic
Education — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 15:06 | 8,917 | -3 |
| 8 Nov 2026, 12:11 | 8,920 | -11 |
| 5 Nov 2026, 08:48 | 8,931 | -13 |
| 2 Nov 2026, 12:17 | 8,944 | -2 |
| 30 Oct 2026, 17:35 | 8,946 | -6 |
| 27 Oct 2026, 13:29 | 8,952 | -9 |
| 24 Oct 2026, 11:54 | 8,961 | -5 |
| 21 Oct 2026, 06:36 | 8,966 | -4 |
| 18 Oct 2026, 02:18 | 8,970 | -12 |
| 15 Oct 2026, 00:46 | 8,982 | -10 |
| 12 Oct 2026, 05:40 | 8,992 | -5 |
| 5 Oct 2026, 10:38 | 8,997 | -20 |
| 27 Sept 2026, 05:55 | 9,017 | -3 |
| 18 Sept 2026, 07:16 | 9,020 | -10 |
| 13 Sept 2026, 23:41 | 9,030 | -8 |
| 9 Sept 2026, 19:55 | 9,038 | -3 |
| 4 Sept 2026, 12:58 | 9,041 | -2 |
| 1 Sept 2026, 03:56 | 9,043 | -4 |
| 28 Aug 2026, 19:34 | 9,047 | -8 |
| 22 Aug 2026, 17:42 | 9,055 | first reading |
Engagement
48 posts held, back to 22 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 52 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.95%
- avg views ÷ 8,917 subscribers
- Avg views / post
- 620
- 28 posts measured
- Reaction rate
- 0.215%
- reactions ÷ views · ER floor
- Posts in window
- 28
- of 48 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 16 of 28 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 48 (22 July 2026 – 13 November 2026) |
| Views total | 17,363 |
| Reactions total | 23 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 13:11 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈2,070
- Videos
- ≈254
- Links
- ≈3,580
Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 28s
- Average length
- 14s
Measured directly from 2 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.
Reaction mix
154 reactions across 33 posts, in 5 distinct kinds. The most used accounts for 25.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 39 | 25.3% | |
| 🥰 | 38 | 24.7% | |
| 👍 | 32 | 20.8% | |
| 🤩 | 29 | 18.8% | |
| 🔥 | 16 | 10.4% |
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 35 of the 48 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 154 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 48 most recent posts we hold, published 22 July 2026 to 13 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 28 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
💥 Три IT-курса по цене одного — только до 15 ноября! Хорошая техническая база - вот что, что помогает разработчику расти и переходить к более сложным задачам. В Proglib Academy можно забрать такую комбинацию для мощной прокачки за 45 990 ₽: 🧠 Алгоритмы и структуры данных — для развития алгоритмического мышления, решения технических задач и подготовки к собеседованиям. 🐍 Python — для практического программирования…
Trace на первом retry не покажет первое падение В CI тест упал, повтор прошёл, а в trace всё выглядит нормально. Сначала проверьте, какую попытку вы записали. Режим on-first-retry в Playwright Test записывает первый повтор теста. Для него должны быть включены retries. Исходная неудачная попытка в эту запись не попадает, даже если именно там проявился баг. Как выбрать режим — Нужен trace первого повтора в CI — выби…
Докачка не должна склеивать разные версии Клиент сохранил первые 500 байт представления длиной 1000 байт и его сильный ETag. Затем отправляет GET с Range: bytes=500-999 и этим валидатором в If-Range. На сервере, который обрабатывает такой Range, проверьте две ветки: — Версия та же: если сервер передаёт весь запрошенный диапазон одной частью, ответ 206 должен содержать Content-Range: bytes 500-999/1000 и соответству…
JSON Patch может сначала проверить значение Допустим, API принимает JSON Patch для смены статуса заявки. Перед изменением клиент добавляет операцию test: текущий статус должен быть draft. Следом идёт replace со значением published. Операции применяются по порядку. При ошибке обработку следует прекратить, а весь patch нельзя считать успешным. Минимальный набор проверок — Статус draft: test проходит, затем применяет…
oneOf: две подходящие ветви дают отказ Число проверяют по двум ветвям JSON Schema: оно кратно 5 и оно кратно 3. Значение 15 подходит обеим. При anyOf это допустимо. При oneOf — ошибка: нужна ровно одна успешная ветвь. Для теста возьмите 10, 9, 15 и 2. Они покрывают совпадение только с первой ветвью, только со второй, с обеими и ни с одной. Если контракт требует взаимоисключающих вариантов, обязательно оставьте слу…
❤1
Ошибка внешнего ключа появилась только в конце В учебной транзакции PostgreSQL 18 сначала удаляют заказ, затем его позиции. Между действиями позиции временно ссылаются на отсутствующий заказ. Можно ли считать успешное удаление заказа багом? Это зависит от настройки внешнего ключа. NO ACTION с отложенной проверкой. Если ключ объявлен допускающим отсрочку и проверка действительно отложена, связь может временно наруш…
Tab ушёл под баннер На странице без действия пользователя появляется закреплённый cookie-баннер. Нажимаете Tab, фокус переходит к ссылке под ним. Ссылка полностью скрыта. Это баг? Подсказка: сначала проверьте, какой уровень доступности требуется продукту. Если требуется WCAG 2.2 AA, это нарушение 2.4.11 Focus Not Obscured (Minimum). Компонент, получивший клавиатурный фокус, не должен быть полностью скрыт интерфейс…
Поле заблокировано. А значение отправилось? В форме номер договора нельзя редактировать. После замены readonly на disabled поле выглядит почти так же, а номер перестаёт приходить на сервер. Для обычного input с типом text, непустым name и значением при нативной отправке формы: — readonly запрещает пользователю менять значение, но поле остаётся в отправляемых данных. — disabled исключает поле из набора данных формы.…
Чужой заказ под вашим токеном В тестовом окружении заведите два аккаунта без общих заказов. По требованиям каждый видит и меняет только свои. Получите ID заказа аккаунта B и подставьте его в запрос аккаунта A, сохранив токен A. Что проверять — Чтение заказа и его вложений не раскрывает чужие данные. — Изменение или удаление не срабатывает. После отказа перечитайте заказ под B и проверьте состояние. — Запрос к собст…
👍1
Клик по «Скачать» ещё не проверяет файл В Playwright ожидание download создают до клика. Иначе событие можно пропустить. const pending = page.waitForEvent('download') await page.getByText('Download file').click() const download = await pending await download.saveAs('artifacts/report.csv') saveAs дожидается завершения скачивания. После сохранения проверьте сам файл по требованиям: например, заголовки колонок и нужн…
Два SELECT в транзакции вернули разное. Это баг? Учебный сценарий: сессия A прочитала 10. Сессия B изменила ту же строку на 20 и сделала COMMIT. A повторила обычный SELECT, не завершая транзакцию. В PostgreSQL при Read Committed второй SELECT может увидеть 20: снимок данных создаётся на начало каждой команды. Это уровень по умолчанию. При Repeatable Read, если первый SELECT уже установил снимок, последующий COMMIT…
❤1
Showing the 12 most recent of 48 posts we hold for @testerlib. 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 7 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.
@testerrjob · 8,19199 postsБиблиотека программиста 🇷🇺
@lib_it3 · 994 postsПубликация вакансий в Proglib.io
@proglib_hh · 3224 postsПрайс - Библиотека программиста (Proglib.io)
@proglib_advertising · 1012 postsФреймворк Django
@django360 · 111 postIT Channels 🌍
@itchannels · 2,0661 postPython в Telegram
@itpython · 171 post
Names
Channels on the register whose handles appear in this channel's posts.
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.
@itevents · 17,272
Telegram ranks this channel #2 of 94 here — alongside 93 others — read 30 September 2026
@serious_tester · 29,726
Telegram ranks this channel #24 of 92 here — alongside 91 others — read 7 September 2026
@godoftesting · 29,147
Telegram ranks this channel #25 of 90 here — alongside 89 others — read 8 September 2026
@qajoboffer · 20,825
Telegram ranks this channel #29 of 92 here — alongside 91 others — read 27 September 2026
@qachanell · 30,126
Telegram ranks this channel #31 of 92 here — alongside 91 others — read 7 September 2026
@forallqa · 22,934
Telegram ranks this channel #38 of 95 here — alongside 94 others — read 20 September 2026
@qa_sklad · 23,087
Telegram ranks this channel #40 of 94 here — alongside 93 others — read 18 September 2026
@frontendproglib · 20,593
Telegram ranks this channel #69 of 93 here — alongside 92 others — read 25 September 2026
This channel appears in 8 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“Библиотека тестировщика | QA, тестирование, quality assurance, manual testing, autotesting, ручное тестирование, автотесты” (@testerlib), 8,917 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/testerlib.
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.