Reading Time and Body Formatting Test
This story is created to verify reading-time calculation and body formatting, including paragraphs, headings, bullet lists, and duplicate-title handling.
Covered by Top slots on AzenPlay.
This is the first paragraph of the story. It is intentionally written as a normal paragraph to verify that the content is displayed correctly on the story page. The paragraph should remain separate from the other paragraphs and should not be combined with them.
The second paragraph contains additional information about the testing process. The content should appear as a separate paragraph, with proper spacing between this paragraph and the previous paragraph. This helps verify that each line or paragraph in the body is rendered according to the expected formatting rules.
Story Overview
This section explains the purpose of the test story. The heading starts with a single hash symbol and should be displayed as a subheading rather than normal paragraph text.
Website Testing
Website testing is an important part of validating a news platform. The tester checks whether the story content, images, navigation, links, filters, and other page elements work correctly. The content should be displayed clearly and consistently across the page.
The story body should support multiple paragraphs without merging unrelated content. Each paragraph should maintain its own structure so that readers can easily understand the information.
Testing Activities
The following activities are included in this test:
- Verify that the story title is displayed correctly.
- Verify that the summary is displayed below the title.
- Verify that the body content is displayed below the image.
- Verify that normal text is displayed as separate paragraphs.
- Verify that headings are displayed correctly.
- Verify that consecutive bullet points are displayed as one bulleted list.
- Verify that the duplicate title is not displayed again as body content.
Reading Time
Reading time should be calculated based on the total number of words in the story content. The expected calculation uses approximately 220 words per minute. A story containing approximately 1,100 words should therefore display approximately 5 min read.
The reading-time value should be visible near the story date. The system should calculate the value consistently and should not display zero minutes for a short story. Short content should display at least 1 min read.
Responsible Gaming
Responsible gaming information should be presented in a clear and readable format. Longer paragraphs should remain readable without unnecessary formatting changes. The body content should preserve the structure entered by the author.
The platform should also ensure that headings are visually different from normal paragraphs. This makes it easier for readers to scan the story and identify different sections.
Events and Publishing
Published stories should display their content correctly after they are created. The body entered by the author should be available on the public story page. Changes made in the content management system should be reflected correctly when the published story is opened.
The story should also maintain the expected navigation elements, source information, sharing options, and related stories where applicable.
Quality Assurance
Quality assurance involves checking the complete story experience from creation to publication. The tester should verify the title, summary, image, body, headings, lists, reading time, and other story elements.
The first line of this body is identical to the story title. The system should recognize this duplicate title and should not display it again as a repeated title in the rendered body. The remaining content should continue normally after the duplicate title line.
The body should also support multiple heading levels. A line beginning with one hash symbol should be rendered as a heading, while a line beginning with two hash symbols should be rendered as a subheading.
Consecutive lines beginning with a hyphen should be grouped together into a single bulleted list. The bullets should not appear as separate unrelated paragraphs.
Final Verification
After publishing the story, open the story page and verify that the reading time is displayed correctly. For this test content, the body should contain approximately 1,100 words so that the expected reading time is approximately 5 min read.
Verify that the duplicate title from the first line of the body is not repeated. Verify that normal paragraphs remain separate. Verify that the heading and subheading formatting is applied correctly. Verify that the bullet points appear as one list.
Finally, confirm that the complete story is readable and that the content structure entered in the admin interface is preserved on the public story page.
Modern digital publishing requires careful attention to how information is collected, processed, reviewed, and presented to readers. A well-structured publishing workflow helps ensure that every story contains accurate information and is displayed consistently across different devices and screen sizes. During quality assurance, testers should verify that the title, summary, category, publication date, source, images, and body content are displayed correctly. They should also confirm that paragraphs remain separated, headings are rendered with the correct hierarchy, and lists are presented in a readable format. Testing should include both short and long stories because different content lengths can affect reading-time calculations. A short story should never display zero minutes, while a longer story should display a reading time that reflects its actual word count. The calculation should be consistent regardless of whether the story contains headings, paragraphs, or bullet points. This makes the reading-time information useful to readers and helps them understand approximately how much time they may need to read the complete story.
Another important part of story validation is checking the content after publication rather than relying only on the authoring interface. The tester should compare the content entered in the administration system with the content displayed on the public story page. Any formatting supported by the publishing system should be preserved when the story is rendered for readers. This includes paragraph spacing, heading levels, bullet lists, links, and other supported content elements. The tester should also verify that duplicate information is not unnecessarily displayed when the same title is entered at the beginning of the body. After making changes to a story, the page should be refreshed and the published version should be checked again to confirm that the latest content is displayed. These checks provide a simple way to validate both the presentation and calculation requirements of the story page. For this test, the final goal is to confirm that a story containing approximately 1,100 words displays approximately five minutes of reading time while maintaining the correct body structure and formatting throughout the page.

