18 tests failing
8/26 passing (31%)Expected is_complete_reply, got "execute_reply"(2)
is_complete_complete, is_complete_incomplete
No stdout containing 'hello'(1)
execute_stdout
No stderr containing 'error'(1)
execute_stderr
execute_reply status: Error(1)
execute_reply_ok
Expected complete_reply, got "execute_reply"(1)
complete_request
Expected inspect_reply, got "execute_reply"(1)
inspect_request
Expected history_reply, got "complete_reply"(1)
history_request
Expected comm_info_reply, got "execute_reply"(1)
comm_info_request
No execute_result on iopub(1)
execute_result
No input_request received on stdin channel(1)
stdin_input_request
Protocol error: Error deserializing content for msg_type `interrupt_reply`: invalid type: null, expected struct InterruptReply(1)
interrupt_request
Counts didn't increment: 8 -> 8(1)
execution_count_increments
Protocol error: Error deserializing content for msg_type `history_reply`: data did not match any variant of untagged enum HistoryEntry(1)
parent_header_correlation
Protocol error: Error deserializing content for msg_type `shutdown_reply`: invalid type: null, expected struct ShutdownReply(1)
shutdown_reply
heartbeat_responds
Kernel responds to heartbeat ping within timeout
heartbeatPass
kernel_info_reply_valid
Kernel returns valid kernel_info_reply with status ok
kernel_info_requestPass
kernel_info_has_language_info
kernel_info_reply contains non-empty language_info.name
kernel_info_requestPass
kernel_info_has_protocol_version
kernel_info_reply contains non-empty protocol_version
kernel_info_requestPass
execute_stdout
Execute code that prints produces stream message on stdout
execute_requestFail
execute_stderr
Execute code that prints to stderr produces stream message
streamFail
execute_reply_ok
Execute valid code returns execute_reply with status ok
execute_requestFail
status_busy_idle_lifecycle
Kernel broadcasts busy then idle status on iopub during execution
statusPass
execute_input_broadcast
Kernel broadcasts execute_input on iopub when executing
execute_inputPass
shutdown_reply
Kernel responds to shutdown request and terminates cleanly
shutdown_requestFail
complete_request
Kernel responds to completion request with complete_reply
complete_requestFail
inspect_request
Kernel responds to inspection request with inspect_reply
inspect_requestFail
is_complete_complete
Kernel correctly identifies complete code as 'complete'
is_complete_requestFail
is_complete_incomplete
Kernel correctly identifies incomplete code as 'incomplete'
is_complete_requestFail
history_request
Kernel responds to history request with history_reply
history_requestFail
comm_info_request
Kernel responds to comm_info request with comm_info_reply
comm_info_requestFail
error_handling
Kernel properly reports errors for invalid syntax
execute_requestPass
display_data
Kernel can produce display_data messages for rich output
display_dataSkip
update_display_data
Kernel can update existing displays via update_display_data
update_display_dataSkip
execute_result
Expression evaluation produces execute_result on iopub
execute_resultFail
rich_execute_result
Expression evaluation produces execute_result with rich MIME types (HTML, images, etc.)
execute_resultSkip
stdin_input_request
Kernel can request input from frontend via stdin channel
input_requestFail
comms_lifecycle
Kernel supports comm open/msg/close lifecycle
comm_openPass
interrupt_request
Kernel responds to interrupt request on control channel
interrupt_requestFail
execution_count_increments
Execution count increments with each execute_request
execute_requestFail
parent_header_correlation
All response messages contain correct parent_header
parent_headerFail