Specialist Preparation Program in Software Testing and Quality Assurance Concepts is a free program on ARPS, the Arab Platform for Professional Studies. Turn software requirements into checkable acceptance conditions and reproducible tests. Record execution and defects, then write an evidence bounded release recommendation. The program covers design, risk, accessibility, authorization, performance and automation.
Optional certificate fee 50% launch discount
$90 instead of $180
331 AED or 338 SAR
Begin with the result a user needs and evidence that could verify it, then distinguish process assurance from product control. Make a time and risk bounded plan. Design cases using equivalence partitions, boundary values, decision tables and state transitions. Choose an appropriate test level, review a specification before execution, and interpret coverage with its limits. Record requests, responses and environments so another tester can repeat a check. Write a defect report that separates observation from possible cause. Use fictional, purpose limited data for performance, accessibility, authorization and recovery checks. Finally, decide what merits automation, diagnose intermittent failures, calculate metrics with clear denominators, and deliver a release recommendation that states evidence, residual risk and decision ownership. All cases are educational; the program does not certify a live system or grant release authority.
Produce reviewable acceptance conditions, test cases, execution and defect records, and a decision memo. Practice separating observations from explanations and assigning the release decision to its owner with bounded evidence.
A passing test does not establish quality across all paths, and high coverage does not establish correct behavior. The program therefore ties every judgment to measured evidence, test data, an oracle, sample limits and residual risk.
Begin by converting a vague booking request into an acceptance condition with starting state, action, observable result, and an independent oracle. Learn why a confirmation on screen does not establish persistence and why an unresolved rule must remain a decision question. Distinguish discovery of a defect in a current build from a process change intended to prevent recurrence. Use impact and likelihood ratings to prioritize cases while keeping the ratings separate from measured probability. Then create a small test plan that traces risk to cases, environment, entry conditions, and exit reporting. The practical outputs are an acceptance table, QA and QC matrix, risk register, and plan that show the release owner what was checked and what remains uncertain.
Design cases from input and workflow rules instead of collecting arbitrary values. Partition a numeric domain into valid and invalid classes, choose representatives, and explain why one representative cannot prove an entire range. Check neighboring boundary values according to data type and precision, separating a system cap from inventory or balance constraints. Turn interacting coupon conditions into a decision table with actions, amounts, and a missing message-priority rule for owner resolution. Finally map return-request states and edges, using independent synthetic records so one case cannot contaminate another. Outputs include class and boundary tables, condition and action rules, a transition diagram, and cases with explicit oracles and evidence limits.
Select a test level for the fact it can reveal: component arithmetic, integration contract, assembled system path, or business acceptance. Do not turn a simulated payment result into a claim about real settlement. Review a contradictory notification specification before execution, converting conflict into an owner decision and then test cases. Interpret branch coverage as an execution map, seeing how a boundary error at 100 can remain despite both branches being traversed. In a bounded exploratory session, inspect mixed Arabic and Latin text, separating stored-data corruption from display ordering. The outputs are a level and evidence map, actionable review record, coverage-gap table, and charter with a reproducible regression case.
This unit protects evidence during execution and after a failure. Build an API execution record identifying build, starting state, account, request key, and stored result rather than treating HTTP 200 as proof of persistence. Convert duplicate effects in a simulated payment into a reproducible defect card, separating severity, repair priority, and an unproven claim of real collection. After a fictional tax-calculation repair, retest the original fault and select regression cases for dependent coupon and refund behavior. Then construct synthetic accounts and invoices for access checks, keeping redacted evidence and cleaning test data. Outputs are an execution log, defect card, regression impact matrix, and data plan that reduces unnecessary exposure.
Examine quality characteristics that one functional pass cannot summarize. Design a performance trial with defined operation, load, period, and denominator, counting successful timely responses separately from fast errors. Check an Arabic booking path through keyboard focus, accessibility-tree names, and error communication, without claiming that one page proves whole-site conformance. Use two synthetic accounts and records for horizontal authorization checks, watching for leaked content even behind a denial status. Inject failure into a simulated notification service, judging booking persistence separately from one-time sending after recovery. Outputs are a load protocol, accessibility checklist, scoped permission case, and recovery matrix, each with the evidence and boundaries of its decision.
Finish by selecting automation for a defined risk, not a large test counter. Compare a repeated API case with an independent oracle against changing marketing language, then prepare isolated data and maintenance rules. Diagnose intermittent checks by separating product delay, an early test timeout, and data collision, retaining every attempt rather than rerunning until green. Calculate progress and pass indicators with named denominators and keep blocked cases and high-impact defects visible beside aggregate rates. In a release memo, connect risks to results from one build and to concrete containment or delay options with an accountable decision owner. The final output is a reviewable conditional recommendation, not approval issued by the specialist on another person's behalf.
Subjects unlock in sequence as you progress.
General concepts draw on the listed ISTQB, quality and web references. Educational cases are original and fictional; citation does not imply publisher endorsement or measured performance of a real system.
A passing test does not establish quality across all paths, and high coverage does not establish correct behavior. The program therefore ties every judgment to measured evidence, test data, an oracle, sample limits and residual risk.
Assessments follow the program blueprint and may use module assessments, a final assessment, or a combination, under the approved attempt policy.
Assessment attempts: 2 per assessment, 7 days apart
The pass mark is announced before the program is published.
The credential confirms completion and successful assessment; it does not represent professional licensure unless explicitly and lawfully stated.
Every certificate has a public verification code. Verify a certificate
The real design with fictional details; opens in a new window.
No. Fictional cases supply the data needed for exercises.
No. You provide a recommendation; the authorized owner decides.
No. It describes exercised structure and does not establish correct results by itself.
No. Textual evidence and tables in the cases support the exercises.
Compare your decision with the option rationale and worked solution, then identify the assumption that changes the judgment.
Yes. Specialist Preparation Program in Software Testing and Quality Assurance Concepts is free on ARPS: every lesson, exercise and assessment is free, the first subject is open to read without an account, and the program is available in Arabic and English. Issuing a certificate is optional; it is a training completion certificate showing you passed the program's assessments, not a university degree, a professional licence or an endorsement by an external body.
The subject of this program is also known as: software testing, quality assurance, software QA, QA testing. Learners usually find it by searching for: software testing course free, software testing life cycle, software testing types, quality assurance courses online, how to become a qa tester.
Programs from the same field or route that may complement what you learn here.
Data, AI, Digital, IT & Cybersecurity
An applied foundation in software testing and quality assurance, moving from requirements and evidence to case design, quality measurement and a conditional release recommendation in a fictional appointment service.
Data, AI, Digital, IT & Cybersecurity
Learn to prepare an initial cloud decision for a small workload using demand, capacity, responsibility, access, recovery and cost evidence. Move from classifying an offer to testing booking, backup, monitoring and migration, then hand over a record of what was shown and what needs owner approval. Cases are fictional and do not grant production authority or professional certification.
Data, AI, Digital, IT & Cybersecurity
Applied preparation for inspectable cybersecurity work products connecting business services, risk, controls, evidence, incidents and improvement decisions.
Data, AI, Digital, IT & Cybersecurity
An applied program that prepares specialists to specify, prompt, test and govern generative-AI work with explicit controls.
