Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- jordanorelli February 2014
- PhiLho February 2014
unit testing?
yesterday I downloaded the Processing source and started tinkering around on it. I noticed that there are a number of relatively straightforward bugs that need fixing so I'd like to lend a hand, but I didn't find any mention of automated tests in the build documentation or the ant files (granted, I don't actually know how to use ant). Since I'm relatively new to the codebase, I was hoping to find some tests that would help verify that any changes I make are cromulent.
is there a unit testing suite in the Processing source? If so, how can I run it?
Answers
processing/app/test/src/test/processing/mode/java and perhaps elsewhere. I suggest to grep for junit in all the .java files.
That said, I mostly saw tests against reported bugs, I don't think there are an extensive set of tests for each and every point of the API.
Beside, they would be hard to do, given the special way the API is made (for ease of use in sketches) and therefore the lack of separation of logic (easy to test) and rendering (depending on a display).
neat! Umm, how would I go about running these? there doesn't seem to be any ant targets defined or anything like that; right now if I want to check that a change I made did what I wanted it to do, I'm running
ant run, loading up a sketch that causes the problem, and then running the sketch. Is that a normal way to go about working on Processing?