The existing snapshots of lexer, parser, and converter would help you understand correctly, by simulating execution in your mind and compared with the snapshots.

btw, you can also make your owned testpoint in bug_playground functions:

mitex/crates/mitex-parser/tests/ast.rs

Lines 41 to 47 in 8e5045a

    
               /// Convenient function to launch/debug a test case 
        
               #[test] 
        
               fn bug_playground() {} 
        
               #[test] 
        
               fn test_easy() { 
        
                   assert_debug_snapshot!(parse(r#"\frac{ a }{ b }"#), @r###"

For example you write a snapshot assertion:

/// Convenient function to launch/debug a test case 
#[test] 
fn bug_playground() {
  assert_debug_snapshot!(parse(r#"\frac{ a }{ b }"#), @"");
}

You can generate the snapshot fastly by cargo insta test --accept. You can also launch debugging by code lenses over bug_playground function to dive in execution:

	/// Convenient function to launch/debug a test case
	#[test]
	fn bug_playground() {}

	#[test]
	fn test_easy() {
	assert_debug_snapshot!(parse(r#"\frac{ a }{ b }"#), @r###"

Architecture.md #146

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions