Setup The Test File, Wrote up what should be

tested first by chunks.

Author: Ebaron96

core/test/processing/core/PFontTest.java

@@ -1,6 +1,7 @@
 package processing.core;
 
 public class PFontTest {
-    //this is a new class to see if I can push to my fork
 
 }
+
+//Write Tests HERE!

core/test/processing/core/PFontTestHelp.txt

@@ -0,0 +1,45 @@
+
+What I think we need to test for broken up into chunks... trying to keep it organized
+
+Chunk A — Construction and initialization
+
+EED TO TEST IF...
+
+the object starts in the correct mode
+important fields are initialized correctly
+lookup structures are prepared correctly
+lazy vs non-lazy behavior is set based on constructor input
+charset input is handled safely and predictably
+
+SOME TEST EXAMPLES...
+
+charset == null should put the font in lazy mode
+ascii array should start filled with -1
+provided charset should be sorted internally, without changing the caller’s original array
+only displayable characters should become glyphs
+ascent/descent get initialized one way or another
+
+Chunk B — Serialization and deserialization
+
+NEED TO TEST IF...
+
+font data can be saved and loaded without corruption
+important metadata survives the round trip
+glyph structure and bitmap data remain consistent
+bad/invalid serialized data fails in the expected way
+
+SOME TEST EXAMPLES...
+
+save a font, reload it, compare glyphCount, size, name, psname, smooth
+glyph widths/heights still match after reload
+invalid stream data should throw instead of silently building a broken font
+
+
+
+Chunk C — Glyph insertion and ordering --will add more if we get through chunks A & B
+Chunk D — Glyph lookup and lazy loading
+Chunk E — Metrics and width calculations
+Chunk F — Native font integration
+Chunk G — Shape generation
+Chunk H — Static charset and font listing
+Chunk I — Glyph inner-class bitmap/header behavior