2 measurements spanning 2 days. 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 65–67 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 01:46
66
no change
7 Aug 2026, 22:05
66
first reading
Engagement
20 posts held, back to 5 December 2022 — 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 22 July 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
1
Links
20
Lifetime counters from Telegram’s own channel header, read 10 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
9 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
3
33.3%
👍
3
33.3%
✍
1
11.1%
❤🔥
1
11.1%
🔥
1
11.1%
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 12 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 9reactions 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 5 December 2022 to 22 July 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.
There are two fields on the registration form: login and password. Does it make sense to use pairwise testing with special tools such as PICT, AllPairs, etc. to test combinations of these fields?
Yes, of course, because it is essential to test combinations of login and password20%
No, because there are too few login and password options to perform pairwise testing30%
No, because the combination reduction algorithm does not make sense to apply to two fields40%
No, pairwise testing is not applicable to the registration form for application security reasons10%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
You are testing an online library and see that in the database the relationship between the entities “book” and “author” is one-to-many. Should you report this as a defect?
No, that's right, because one writer usually writes multiple books11%
Yes, it's a defect, we should put the author in the “books” table, this realization speeds up the DB0%
Yes, it's a defect, there should be a "many-to-many" relation56%
Testers never test database relations, this is the job of programmers and database analysts33%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
After performing some operation on the UI, a three-tier web application generated an error “Internal Server Error 500”. At what application layer can the root cause of this error be located?
On the UI, that's where we performed the operation.0%
The server is to blame, it's a server error.75%
At the database level. That's where the incorrect data came from.0%
At any of the levels. Without additional information it is impossible to say unambiguously.25%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
The application includes functionality A, B, C. The new release is released with new functionality D, which affected C but had no effect on A and B.
Which tests should be included in the final testing of the new release on staging?
Smoke of A, B, C, D.0%
Smoke of A, B, C, full D testing11%
Smoke of A, B, sanity of C, full testing of D89%
Full testing of all functionality.0%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
What interesting has been there in professional QA education lately:
🇺🇸 Continued to organize internships at US companies
✏️ Conducted open exams
Maxim and Anna
👩🏫 New open classes
There are x days left to work as a tester
How to become a competitive software tester?
Git for QA
Docker for QA
Relational Databases for QA
What is exploratory testing?
Entrance tests for Pre-Middle QA Manual testing + Internship cour…
What’s been going on for the last two months?
📖 The full release of the free 100-Year QA-textbook, an interactive QA tutorial of 42 modules, 42+ online tests from mentors with a combined experience of 100+ years, was out.
🦾 Now you can learn the QA profession from cover to cover using the textbook with built-in tests and homework!
♻️ We have moved to full-cycle training. Now the training is not just lectures + HWs …
You have the task of testing a web application in multiple browsers and on multiple operating systems. What is the best test-design method for this case?
Equivalence classes15%
Decision tables23%
Pairwise testing62%
Cause-effect diagrams0%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🤔 What interesting things have been happening in recent weeks?
🎙 We continue the series of streams:
10 signs of a QA course quality
- A video about the difference between commercial and professional education
What is an ideal QA internship?
- QA interns and mentor analyze the question in details.
What is the software tester profession? Reasons to work in IT? What about $$$?
- Here the most interesting is the rang…
Showing the 12 most recent of 20 posts we hold for @Mentorpiece. 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.
Polls
The 6 most recent of 13 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.
There are two fields on the registration form: login and password. Does it make sense to use pairwise testing with special tools such as PICT, AllPairs, etc. to test combinations of these fields?
Yes, of course, because it is essential to test combinations of login and password20%
No, because there are too few login and password options to perform pairwise testing30%
No, because the combination reduction algorithm does not make sense to apply to two fields40%
No, pairwise testing is not applicable to the registration form for application security reasons10%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
You are testing an online library and see that in the database the relationship between the entities “book” and “author” is one-to-many. Should you report this as a defect?
No, that's right, because one writer usually writes multiple books11%
Yes, it's a defect, we should put the author in the “books” table, this realization speeds up the DB0%
Yes, it's a defect, there should be a "many-to-many" relation56%
Testers never test database relations, this is the job of programmers and database analysts33%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
After performing some operation on the UI, a three-tier web application generated an error “Internal Server Error 500”. At what application layer can the root cause of this error be located?
On the UI, that's where we performed the operation.0%
The server is to blame, it's a server error.75%
At the database level. That's where the incorrect data came from.0%
At any of the levels. Without additional information it is impossible to say unambiguously.25%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
The application includes functionality A, B, C. The new release is released with new functionality D, which affected C but had no effect on A and B.
Which tests should be included in the final testing of the new release on staging?
Smoke of A, B, C, D.0%
Smoke of A, B, C, full D testing11%
Smoke of A, B, sanity of C, full testing of D89%
Full testing of all functionality.0%
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 5 December 2022 to 22 July 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.
Mentions
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.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“Mentorpiece Central” (@Mentorpiece), 66 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Mentorpiece.
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.