| Test ID | Scenario | Steps | Expected Result |
|---------|----------|-------|-----------------|
| AT‑1 | Page loads | Visit nepaliputi.net/pu-ti | Dictionary card appears, audio icon present, top examples displayed |
| AT‑2 | Audio playback | Click audio icon | 0.5‑second audio clip plays without error |
| AT‑3 | Submit example (guest) | Fill form → Submit | Captcha challenges; after success, entry appears in moderation queue |
| AT‑4 | Approve submission (moderator) | Moderator clicks “Approve” | Example appears instantly in the top‑voted list (if votes ≥ 0) |
| AT‑5 | Vote on example | Click ▲ on an example | Vote count increments by 1; button disables for that user |
| AT‑6 | Bookmark | Click “Star” | Entry saved to user’s profile; a notification badge appears on “Bookmarks” |
| AT‑7 | SEO markup validation | Run Google Structured Data Testing Tool on page URL | JSON‑LD passes without errors; DefinedTerm includes audio URL |
| AT‑8 | Accessibility | Navigate using only Tab/Enter keys | All interactive elements reachable; audio button has ARIA label “Play pronunciation of पुती” |
| AT‑9 | Performance | Load page on throttled 3G (Chrome DevTools) | Page fully renders within 1.5 s, audio file < 30 KB |
| Phase | Duration | Milestones |
|-------|----------|------------|
| Phase 1 – MVP | 4 weeks | • Dictionary card with audio
• Static top‑voted examples (seed data)
• Submit form → moderation queue |
| Phase 2 – Community | 3 weeks | • Voting system
• Q&A thread
• Bookmark + notification |
| Phase 3 – SEO & Analytics | 2 weeks | • Structured data markup
• Export API (CSV/JSON)
• Performance & accessibility audit |
| Phase 4 – Polish & Scale | 2 weeks | • CDN caching strategy
• Rate‑limit & anti‑spam
• Multi‑language UI (English ↔ Nepali) |
| Phase 5 – Launch | 1 week | • Soft launch to beta users
• Collect feedback, iterate on moderation workflow | nepali puti net com
| Category | Strengths | Suggested Enhancements |
|----------|-----------|------------------------|
| News Reporting | • Timely coverage of local events and breaking news.
• Use of Nepali script throughout, which caters to the primary readership. | • Provide a brief author bio and source attribution for greater credibility.
• Add a “Fact‑Check” badge for high‑impact stories. |
| Community Articles | • Platform for user‑submitted stories, poetry, and opinion pieces—great for community engagement. | • Moderate submissions to filter out spam and maintain editorial standards.
• Introduce a rating or “most‑read” widget to surface high‑quality contributions. |
| Multimedia | • Embeds of YouTube videos and audio clips enrich the reading experience. | • Host locally relevant videos on a CDN to reduce buffering for users with limited bandwidth. |
| SEO & Discoverability | • Proper use of <title> tags and meta descriptions for most pages.
• URL structure is clean and language‑friendly (e.g., /news/2024/04/14/prime-minister-speech). | • Add structured data (Schema.org Article markup) to improve visibility in Google News.
• Implement an XML sitemap and submit it to Google Search Console. | | Test ID | Scenario | Steps |
| # | Requirement | Acceptance Criteria | |---|-------------|----------------------| | NFR‑1 | Performance | Dictionary page loads ≤ 1.5 s on 3G; audio file ≤ 30 KB. | | NFR‑2 | Scalability | System must handle 5 000 concurrent users (peak traffic) without degradation. | | NFR‑3 | Accessibility | All UI components meet WCAG 2.1 AA (ARIA labels for audio, keyboard navigation). | | NFR‑4 | Security | Input sanitized to prevent XSS/SQLi; rate‑limit submissions to ≤ 5 per minute per IP. | | NFR‑5 | Localization | UI strings available in English and Nepali (fallback to English). | | NFR‑6 | Data Retention | User‑generated content retained for a minimum of 2 years unless flagged for removal. | | NFR‑7 | Backup | Daily DB snapshots; audio files stored in CDN with versioning. | | Category | Strengths | Suggested Enhancements |
| Aspect | What Works Well | Opportunities for Improvement |
|--------|----------------|--------------------------------|
| Visual Design | • Clean, white‑dominant layout that reduces visual clutter.
• Consistent typography using Nepali Unicode fonts, which improves readability for the target audience. | • Add a subtle accent color or graphic element to give the site a stronger visual identity.
• Optimize contrast ratios for better accessibility (especially for users with low vision). |
| Navigation | • Straight‑forward top‑menu (Home, News, Entertainment, Lifestyle, Forum, About).
• Breadcrumbs on article pages help users understand their location. | • Consider a sticky navigation bar so users can switch sections without scrolling back to the top.
• Add a quick “Back to Top” button for long‑form articles. |
| Mobile Responsiveness | • Layout adjusts fluidly on smartphones and tablets.
• Touch‑friendly buttons and tap targets. | • Some images stretch slightly on very small screens; using object-fit: cover would keep aspect ratios intact.
• Reduce the number of ads shown on mobile to improve load speed. |
| Loading Speed | • Main landing page loads under 2 seconds on a standard 4G connection (thanks to compressed images and minified CSS/JS). | • Implement lazy‑loading for off‑screen images and embed videos.
• Leverage browser caching for static assets to shave off an extra 0.5‑1 second on repeat visits. |
| ID | Requirement | Details |
|----|-------------|---------|
| FR‑1 | Dictionary Card | Shows Nepali term, transliteration, English translation, part‑of‑speech, audio icon, and a short definition. |
| FR‑2 | Audio Playback | Uses pre‑recorded native speaker audio (MP3 ≤ 30 KB). Fallback to text‑to‑speech if missing. |
| FR‑3 | Example List | Displays up to 5 “top‑voted” community examples, each with:
– Example sentence (both languages)
– Contributor username (link to profile)
– Up/Down vote buttons |
| FR‑4 | Submit Form | Inline form with:
– Text area for Nepali example
– Text area for English translation
– Optional “region/dialect” tag
– Captcha/Rate‑limit |
| FR‑5 | Moderation Queue | New submissions go to a queue visible only to moderators; each entry shows submitter, timestamps, and a “Approve/Reject” button. |
| FR‑6 | Voting System | Users can vote once per example (tracked via cookie + user‑account). Vote count updates in real time (WebSocket or polling). |
| FR‑7 | Bookmark & Notification | “Star” button adds entry to user’s saved list; optional email or in‑app push when new examples pass moderation. |
| FR‑8 | Q&A Thread | Collapsible panel below the dictionary card for user questions, with threaded replies, voting, and moderation. |
| FR‑9 | SEO Markup | JSON‑LD schema.org DefinedTermSet with a DefinedTerm for पुती. Include audio, exampleOfWork, inLanguage, etc. |
| FR‑10 | Analytics | Track: page views, audio plays, submissions, approvals, votes, and question interactions. Exportable via admin dashboard. |