Channel
@bugbuster_news
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Declared links · Cite this entry
321subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002526150485 |
|---|---|
| Type | Channel |
| Username | @bugbuster_news |
| Description | https://github.com/BugBuster-AI/bugbuster Пишите E2E автотесты на естественном языке — без кода, без боли. В канале: анонсы релизов, новых фичей, мероприятий и ответы на вопросы о платформе. |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bugbuster_news |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 07:31 | 321 | no change |
| 8 Aug 2026, 07:15 | 321 | first reading |
20 posts held, back to 29 September 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 pageof 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 15 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
119 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 37.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 44 | 37.0% | |
| 🔥 | 44 | 37.0% | |
| ❤ | 17 | 14.3% | |
| ❤🔥 | 6 | 5.04% | |
| 🎄 | 4 | 3.36% | |
| 🎉 | 3 | 2.52% | |
| ⚡ | 1 | 0.84% |
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 119reactions 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 29 September 2025 to 15 May 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.
Всем привет!👋 Решил под конец недели сделать небольшой анонс, на скорую руку))) Очень скоро на платформе появится автоматизация android приложений. И на видео можно посмотреть как это будет выглядеть. 😉
👍3❤🔥2
Signed Даниил Ахетов
Вышел релиз v0.2.0! 🚀 И я наконец-то добрался, чтобы записать видео. В релиз вошла генерация кода. На видео постарался подробно, но сжато рассказать как это работает. Это не последняя итерация, генерация еще будет улучшаться, но релиз необходим, чтобы продолжить работу над автоматизацией мобильных и нативных платформ. Думаю, что скоро будет анонс по мобилкам 😊 Еще появилась документация, теперь она живет тут https…
👍5❤3
Signed Даниил Ахетов
Я не выдержал 😊 Буквально вчера я выложил PR с генерацией кода https://github.com/BugBuster-AI/bugbuster/pull/21 Код еще не причесан, но в таком виде он провисит еще как минимум неделю, так что можно накидывать в комментарии, буду крайне благодарен) 🙏 Не пугайтесь количеству измененных файлов, в этом PR удален по сути целый сервис playwright-custom. Специально все разбил по коммитам, чтобы было проще разобраться. …
❤🔥4⚡1❤1🔥1
Signed Даниил Ахетов
Posted without readable text
Posted without readable text
Всем привет! 👋 Генерация кода автотестов в процессе разработки. 🔥 В качестве языка был выбран JavaScript, и вспомнилась одна забавная особенность: let i = 0; console.log(i++); // 0 console.log(++i); // 2 Один и тот же оператор, казалось бы… 🤔 Но в первом случае значение возвращается до инкремента, во втором — после. В тестах такие нюансы легко превращаются в неожиданные результаты. 🤯 ❓А какие у вас любимые «стр…
🔥3
Channel name was changed to «BugBuster Open Source AI TMS»
Channel name was changed to «BugBuster AI Open Source TMS»
Всем привет! 👋 У нас потрясающая новость! BugBuster переезжает в OpenSource 🎉 https://github.com/BugBuster-AI/bugbuster Платформу мы не бросаем, она продолжит развиваться. В ближайшее время репозиторий наполнится документацией, в нем уже есть ReadMe, по которому можно развернуть платформу локально. ❗️SaaS платформу мы закрываем, уже на следующей неделе сервера перестанут работать. Домен bug-buster.ru остается на …
👍1🔥1
Коллеги, привет! 👋 🚀 Выпускаем сразу две версии — 3.5.0 и 3.6.0 (объединили изменения в один релизный анонс) В этот раз основной фокус — на упрощении создания и редактирования тест-кейсов. Запись сценария, добавление шагов и работа с данными стали удобнее. Идея теста быстрее превращается в рабочий сценарий. Подробности: 🎙 Рекордер Действия, записанные через плагин, корректно превращаются в сценарий одной кнопкой.…
🔥6👍4❤1
Всем привет! 👋 🚀 Мы выпустили BugBuster 3.4.0 (и заодно рассказываем про 3.3.0 — он вышел раньше, но без публичного анонса) Эти обновления усиливают контроль при работе с UI-тестами. У вас появилось больше инструментов, которые помогают уточнить, какой именно элемент интерфейса имеется в виду в описании шага, и упростить отладку сценариев. Что это даёт на практике: 🧭 Точнее находить элементы в сложных интерфейсах…
🔥8👍2
✨ Коллеги, друзья, единомышленники! Команда BugBuster поздравляет вас с наступающим Новым годом 🎉 Прошедший год получился очень насыщенным: мы сделали много важных шагов, и часть из них даже не успевали анонсировать. Спасибо вам за участие в бета-тестировании, обратную связь и интерес к продукту - без вас этого пути просто не было бы. В следующем году планируем чаще делиться новостями о развитии платформы и расска…
🎄4🎉3🔥2
Showing the 12 most recent of 20 posts we hold for @bugbuster_news. 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.
Citation-graph rank — 949,370 of 1,350,102entries 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.
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.
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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association— we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. 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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“BugBuster Open Source AI TMS” (@bugbuster_news), 321 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/bugbuster_news.
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.