Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan
Distinct Failing Test Cases
00:00
5 left

Distinct Failing Test Cases

EasySQL · PostgreSQL

Problem

Write a SQL query to find the number of distinct failing test cases per release.

Use the test_results table. Count only rows whose status is FAIL, and exclude releases with no failing test cases.

Output

  1. One row per release with at least one failure
  2. Columns: release and distinct_failing_test_cases
  3. Sort by release in ascending order

Schema

test_results
ColumnTypeDescription
result_idPKINTUnique identifier for a test result
releaseVARCHAR(50)Release tested
test_case_idVARCHAR(50)Identifier of the executed test case
statusVARCHAR(20)Test result status, such as PASS or FAIL
Tablestest_results
Interviewer

Your question is Distinct Failing Test Cases. Start with the requirements and the one table in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePostgreSQL
Sign up free to run your codeLog inLn 1
Run your query to see results here.