-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add SequencerSpecificEvent , and empty!(::MIDITrack)
#173
Conversation
Thank you for your review. If you decide merge, please make a new release, thank you very much. |
Thank you for your review! I have finished all the suggested changes. |
@@ -31,4 +31,11 @@ | |||
@test_throws errtype MIDI.readsysexevent(Int(input[1]), IOBuffer(input[2:length(input)])) | |||
end | |||
end | |||
|
|||
@testset "SequencerSpecificEvent" begin | |||
midi = load("SequencerSpecific.mid") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't undertstand what you are doing here. You are loading this midi data, but you don't use them next in the test suite...? The current test suite is meaningless you are only testing whether you initialized the SequencerSpecificEvent
with the values you initialized it with. Rather trivial, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I don't think it's necessary to actually use this midi data.
If the added code is incorrect, an error will be throwed on this line when initialization, and causing the test to fail.
The fact that no exception is thrown already indicates that SequencerSpecificEvent
is being parsed and instantiated correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests have been added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What, no not at all. What we want to know is whether we correctly find this special midi type in an actual midi track that we load. Instantiating the type is trivial, you aren't testing anything really if you only test that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But now we have this midi file, and it is very small, so thank you, this is exactly what I was asking for!
Also implement |
empty!(::MIDITrack)
@@ -31,4 +31,11 @@ | |||
@test_throws errtype MIDI.readsysexevent(Int(input[1]), IOBuffer(input[2:length(input)])) | |||
end | |||
end | |||
|
|||
@testset "SequencerSpecificEvent" begin | |||
midi = load("SequencerSpecific.mid") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But now we have this midi file, and it is very small, so thank you, this is exactly what I was asking for!
@Datseris Hi, would you mind make a new release? Thank you very much 😊👍 |
Related issue #172