Objective: Build an app that is functionally similar to this.
Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style.
-
I should be able to see an outer container with a corresponding
id="drum-machine"
that contains all other elements. -
Within
#drum-machine
I can see an element with a correspondingid="display"
. -
Within
#drum-machine
I can see 9 clickable drum pad elements, each with a class name of drum-pad, a unique id that describes the audio clip the drum pad will be set up to trigger, and an inner text that corresponds to one of the following keys on the keyboard:Q
,W
,E
,A
,S
,D
,Z
,X
,C
. The drum pads MUST be in this order. -
Within each
.drum-pad
, there should be an HTML5 audio element which has a src attribute pointing to an audio clip, a class name of clip, and an id corresponding to the inner text of its parent.drum-pad
(e.g.id="Q"
,id="W"
,id="E"
etc.). -
When I click on a
.drum-pad
element, the audio clip contained in its child audio element should be triggered. -
When I press the trigger key associated with each
.drum-pad
, the audio clip contained in its child audio element should be triggered (e.g. pressing theQ
key should trigger the drum pad which contains the stringQ
, pressing theW
key should trigger the drum pad which contains the stringW
, etc.). -
When a
.drum-pad
is triggered, a string describing the associated audio clip is displayed as the inner text of the#display
element (each string must be unique).