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
ExperiencesCoaching
New
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess 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
Get started
Validate Test Lifecycle Sequence
00:00
5 left

Validate Test Lifecycle Sequence

MediumPython

Problem

Given a list of lifecycle event strings events, determine whether the sequence is valid. Each event is one of "PLAN", "EXECUTE", "DEFECT", "RETEST", or "CLOSE". A valid sequence must follow these rules: PLAN must occur before any other event, EXECUTE can occur only after PLAN, every DEFECT must be matched by a later RETEST, and CLOSE can appear only once at the end after all defects have been retested. Return True if the sequence is valid, otherwise return False.

Constraints

  • 1 <= len(events) <= 10^5
  • Each events[i] is one of "PLAN", "EXECUTE", "DEFECT", "RETEST", "CLOSE"
  • CLOSE, if present, must be the final event in a valid sequence

Function Signature

def validate_lifecycle(events):
Interviewer

Your question is Validate Test Lifecycle Sequence. Start with the requirements 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.
Code
Sign up free to run your codeLog inLn 2
Run your code to see test output here.