Does Siksha Sarovar have an AI chatbot to answer student doubts?

Yes. Siksha Sarovar has a built-in AI Assistant chatbot accessible from a floating button on every page. It understands English, Hindi and Hinglish, handles typos (for example 'pyhtion' or 'certifecate'), and indexes 165+ destinations including every course, lesson, BCA subject, school chapter, competitive exam topic, FAQ and tool. Most queries return direct link cards in under 5 milliseconds. An AI fallback is available for novel questions.

Can I ask the SikshaSarovar chatbot questions in Hindi or Hinglish?

Absolutely. The chatbot is built specifically for Indian students — natural Hinglish queries like 'kaise milega certificate', 'free hai kya', 'pyhtion ke datatype kaha hai', 'kaha se shuru karu' are first-class citizens. The matcher strips Hindi filler words and routes you to the right course, lesson or page.

Is the SikshaSarovar AI chatbot free to use?

Yes. The chatbot is 100% free, requires no signup, and is available on every page. It runs locally in your browser for the vast majority of queries — there is no API cost or usage limit. The optional 'Ask AI' fallback for advanced coding questions uses the Pro AI Tutor.

Is Siksha Sarovar really free?

Yes. Every course, lesson, quiz, online compiler, and notes download is free to use without an account. We offer an optional Pro pass that unlocks longer AI tutor sessions, larger compiler quotas and priority support, but it is not required to learn from the platform. The educational content itself stays free.

Do I need to sign in to use the courses?

No. You can browse any course, read all lessons, run code in the compiler and take quizzes without signing in. Google Sign-In is purely optional and is used only to save your progress, quiz scores and certificate eligibility across devices. We never request access to Gmail, Drive, Calendar, Contacts, or any sensitive Google data.

Are the certificates from Siksha Sarovar recognised?

Our certificates are a record of completion that you can share on LinkedIn or attach to applications, but Siksha Sarovar is an independent platform — not a UGC-recognised university or board. We are upfront about that. The certificate is most useful as a verifiable signal that you have completed the curriculum, not as a substitute for a degree.

Which courses are best for BCA and MCA students?

Our University Curriculum section covers the YMCA BCA/MCA syllabus subject-by-subject — Data Structures, DBMS, Web Based Programming, Computer Networks, Operating Systems, Software Engineering, Data Warehousing and more. Each subject is broken down into the same units your university teaches, with previous year question papers where available.

Can I use Siksha Sarovar to prepare for SSC, UPSC, Banking or Railway exams?

Yes. The Competitive section has dedicated tracks for SSC (CGL, CHSL, MTS), UPSC, IBPS/SBI Banking, RRB Railways and defence exams (NDA, CDS, AFCAT). Topics include quantitative aptitude, reasoning, English grammar, general knowledge and current affairs, written specifically for the Indian exam pattern.

What languages does the online compiler support?

The Siksha Sarovar online compiler supports C, C++, Python, Java, PHP, JavaScript, C# and SQL. The compiler runs your code in a sandboxed environment using Judge0, returns the standard output and error stream, and supports stdin so you can test interactive programs. There is no installation — everything runs in your browser.

How is my personal data handled by Siksha Sarovar?

We follow data minimisation: we collect only what is needed (email, name, profile picture from Google sign-in, and your learning progress). Data is stored on Supabase with HTTPS in transit. We do not sell user data, and we do not use it to train AI models. You can request deletion at any time by emailing contact@sikshasarovar.com — see our Privacy Policy for the full details.

Who founded Siksha Sarovar?

Siksha Sarovar was founded by Rohit Kumar, who serves as CEO and Head Developer. Rohit built the platform to provide free, structured education to students across India — covering programming courses, university notes, school study material and competitive exam preparation.

Unit 3.3: Acceptance Testing — Software Testing Notes

Unit 3.3: Acceptance Testing & Types

1. User Acceptance Testing (UAT)

Definition: The final phase of testing. It is performed by the Client or End Users, not the technical team. The goal is not to find bugs, but to gain confidence that the system is ready for business use.

Entry Criteria: System Testing is 100% passed. Critical bugs are fixed. Exit Criteria: Client signs off the "Go Live" document.

---

2. Types of Acceptance Testing

A. Alpha Testing

Definition: Testing performed by potential users/customers or an independent test team at the developer's site.
Environment: Controlled lab environment.
Role: Developers are present ("Over the shoulder" observation). They can fix bugs immediately.
Goal: To simulate real users but in a safe space to catch glaring issues before the public sees them.

B. Beta Testing

Definition: Testing performed by real users of the software application in a real environment (User's site).
Environment: Uncontrolled, Live environment (Real networks, real data).
Role: Developers are NOT present. They rely on "Feedback Forms" or "Crash Logs" sent by users.
Goal: To test reliability, compatibility, and usability in the chaotic real world.
Example: "Early Access" games on Steam.

Detailed Comparison: Alpha vs Beta

Feature	Alpha Testing	Beta Testing
Where?	Developer's Lab (Factory).	User's Home/Office (Real World).
Who?	Internal employees / Selected users.	Public / Actual Customers.
Data used	Dummy/Test Data.	Real/Live Data.
Timing	Before Beta.	Before Final Release (Gold).
Box Type	Often White/Grey Box insights.	Pure Black Box.

C. Operational Acceptance Testing (OAT)

Focuses on the "IT Management" side, not the "User" side.
Checks: Backup/Restore procedures, Disaster Recovery, Maintenance capability, Security compliance.
Audience: System Admins, DevOps Engineers.

D. Contract Acceptance Testing

Testing against strictly defined criteria in the contract (SLA).
Example: "The contract says the page must load in 2 seconds." Testing specifically for that number. It's a Pass/Fail business decision.