Channel

QA в 1C — все о тестировании в мире 1С

@QA_1C

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

655subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID	-1002886846268
Type	Channel
Username	@QA_1C
Description	Канал посвящен вопросам обеспечения качества в решениях на платформе 1С. Автор — Александр Кунташов, ведущий специалист ИНФОСТАРТ Лаборатории, тренер курса по автоматизации тестирования в 1С при помощи Vanessa Automation: infostart.ru/va-course
Created	Between 1 June 2025 and 31 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	6 August 2026
Last confirmed live	13 August 2026
Measurements held	2
On Telegram	t.me/QA_1C

Growth

2 measurements taken within a single day. 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 654–656 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
6 Aug 2026, 17:18	655	no change
6 Aug 2026, 08:47	655	first reading

Engagement

20 posts held, back to 20 October 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 19 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos: 19
Videos: 4
Links: 34

Lifetime counters from Telegram’s own channel header, read 6 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.

Reaction mix

242 reactions across 18 posts, in 20 distinct kinds. The most used accounts for 43.0% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
🔥	104	43.0%
👍	63	26.0%
❤	22	9.09%
❤‍🔥	15	6.20%
🎉	7	2.89%
custom 5224496354562175945	6	2.48%
✍	4	1.65%
🤯	4	1.65%
⚡	2	0.826%
💯	2	0.826%
😱	2	0.826%
🙏	2	0.826%
🤝	2	0.826%
custom 5343871895357903798	1	0.413%
🎄	1	0.413%
🏆	1	0.413%
👀	1	0.413%
👌	1	0.413%
💩	1	0.413%
🤔	1	0.413%

Custom emoji. 2 of the rows above are 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 counts beside them areTelegram’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 18 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 242reactions 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 20 October 2025 to 19 June 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

19 Jun 2026, 15:47 UTC381 views7 reactionsread 6 August 2026

Forwarded from @TECH_EVENT_INFOSTARTVideo

🎙 Продолжаем знакомить вас с модераторами INFOSTART TECH EVENT 2026 и их докладами Александр Кунташов, модератор секции «QA: Тестирование и качество ПО», выступит с докладом: 💭 «AI-assisted testing для легаси-систем: стратегии, промпты, ограничения и практические подходы» Легаси-системы редко бывают идеальной средой для автоматизации тестирования. Отсутствие актуальной документации, сложная бизнес-логика и высокий…

🔥5custom 52244963545621759452

22 May 2026, 09:33 UTC550 viewsread 6 August 2026

Ответ в @testspro1c получился полноценной инструкцией, не правильно было бы не репостнуть в свой же канал 😎

22 May 2026, 09:33 UTC755 views21 reactionsread 6 August 2026

Как запустить Vanessa Automation MCP (быстрый старт) По настройке/запуску там все просто: 1. Качаете последний релиз VA 2. В базу, в которой запускаете менеджер тестирования ставите расширение onec-client-mcp-devkit (флаги "Безопасный режим" и "Защита от опасных действий" снимаем) 3. Опционально в базе, к которой будет подключаться клиент тестирования, ставите VAExtension.cfe (чтобы максимально доступны были шаги…

🔥16⚡2👍2✍1

21 May 2026, 19:24 UTCviews —

QA в 1C — все о тестировании в мире 1С pinned a photo

21 May 2026, 11:43 UTC827 views7 reactionsread 6 August 2026

Photo

🤟 Секция «QA: Тестирование и качество ПО» снова ждет ваши темы на INFOSTART TECH EVENT 2026! На INFOSTART TECH EVENT 2026 открыт прием заявок на доклады — и секция «QA: Тестирование и качество ПО» снова ждет ваши темы. Конференция пройдет 8–10 октября 2026 года в Санкт-Петербурге, в отеле «Санкт-Петербург». В программе — 7 технических секций, 130+ докладов, живое общение с коллегами и участниками сообщества 1С. ➡️…

custom 52244963545621759453❤2🔥2

20 Apr 2026, 07:36 UTC576 views11 reactionsread 6 August 2026

Forwarded from @VanessaAutomation

Опубликован релиз 1.2.043.12 Описание изменений в релизе тут. Добавлена поддержка работы с ИИ. Подробнее тут.

🔥9👍2

29 Jan 2026, 10:53 UTC≈1,180 views13 reactionsread 6 August 2026

Photo

✔️ Новый канал на тему обеспечения качества и тестирования в 1С — Будни 1С QA Тема QA в мире 1С потихонечку разгоняется и прогревается, и вот новый канал: Будни 1С QA. Автор — Татьяна Головкина, руководит в OZONе одной из крупнейших команд тестировщиков 1С, модератор секции QA на прошлогоднем INFOSTART TECH EVENT. Рекомендую, потому что Татьяне точно есть что рассказать про автоматизацию тестирования решений на 1С …

❤‍🔥8👍4💩1

16 Jan 2026, 09:34 UTC≈1,770 views24 reactionsread 6 August 2026

✅ Рубрика #ВопросОтвет теперь в формате видеоинструкций, сделанных при помощи Vanessa Automation! Я уже упоминал, что Леонид Паутов (автор и главный разработчик ✅ Vanessa Automation) сделал классную вещь: он взял наши с вами вопросы-ответы из рубрики #ВопросОтвет и превратил их в видео. Самое крутое здесь то, как это сделано: инструкции созданы средствами самой Vanessa Automation — при помощи механизма видеосценари…

🔥20❤‍🔥3custom 53438718953579037981

30 Dec 2025, 08:29 UTC916 views9 reactionsread 6 August 2026

Photo

🦋 [#Вебинар] TurboGherkin — современный язык автоматизации тестирования Всех с наступающим Новым годом! 🎄 Желаю мира, благополучия и профессионального роста! В конце января стартует новый поток курса «Автоматизированное тестирование в 1С». Традиционно перед стартом мы с 🤓 Инфостарт Обучением проводим бесплатный открытый вебинар. О чем будем говорить? На прошлых вебинарах мы решали конкретные практические задачи…

❤‍🔥4✍3🎄1custom 52244963545621759451

29 Dec 2025, 16:30 UTC782 views6 reactionsread 6 August 2026

Forwarded from @orgprog

Сегодня выпуск дебаты юнит тесты vs интеграционные с Александром Макаровым. В видео капец как много полезного + мы прошлись по реальным репам, посмотрели и обсудили их тесты youtube.com/watch?v=MhdRKBkOvtg Альтернативные ссылки: Аудио | vk

🔥4👍2

27 Dec 2025, 15:46 UTC641 views9 reactionsread 6 August 2026

Forwarded from @radio_ingvarPhoto

Merge Orenburg | IT Fest Апресов Игорь, Об инструментах тестирования в 1С Эта лекция об истории развития тестирования в вертикали 1С:Предприятия. Ректроспективный обзор технологий и событий. 📺 Смотреть на VK 📺 Смотреть на Rutube 📺 Смотреть на YouTube Ранее уже публиковал, только на YouTube, и с не очень приятным качеством. Получилось немного исправить, смотреть стало приятнее.

👍5🔥4

27 Nov 2025, 09:33 UTC≈1,170 views16 reactionsread 6 August 2026

Photo

🦋 [#Видео] Структура сценария (Scenario Outline) в TurboGherkin — полный урок из курса «Автоматизированное тестирование в 1С» Конструкция Структура сценария (Scenario Outline) очень недооценена и используется на практике довольно редко. По отзывам участников курса Инфостарта по автоматизированному тестированию, не все знакомы с этой конструкцией в принципе, а те, кто знакомы, не знают тонкостей. При этом я не один…

❤7👍7🔥2

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

Citation-graph rank — 809,353 of 1,345,403entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Будни 1С QA
@daily1cqa · 2161 post Александр Кунташов — про 1С и не только
@kuntashov_devnotes · 2,5411 post

Republishes

Channels on the register whose posts this channel has forwarded.

Организованное программирование | Кирилл Мокевнин
@orgprog · 13,9271 post Ozon Tech
@ozon_tech · 28,4481 post Игорь Апресов | Radio Ingvar
@radio_ingvar · 2,3251 post INFOSTART TECH EVENT ⚙️
@TECH_EVENT_INFOSTART · 1,1131 post Vanessa Automation
@VanessaAutomation · 2,2741 post

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.

Named by

Channels on the register whose posts name this channel's handle.

Александр Кунташов — про 1С и не только
@kuntashov_devnotes · 2,5412 posts Будни 1С QA
@daily1cqa · 2161 post

Names

Channels on the register whose handles appear in this channel's posts.

Будни 1С QA
@daily1cqa · 2162 posts Инфостарт.Обучение
@infostart_edu · 1,1941 post Игорь Апресов | Radio Ingvar
@radio_ingvar · 2,3251 post Vanessa Automation
@VanessaAutomation · 2,2741 post

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

“QA в 1C — все о тестировании в мире 1С” (@QA_1C), 655 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/QA_1C.

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.