Yeah, I know I can go through postmeta table and list all the fields, but I’m trying to avoid that.
I even thought of hooking to post save and trying to see what will be saved there, but this seemed like too much work for setting up automated tests.
Well, if there are no simple ways of doing that I’ll just avoid testing this part, until I can just refactor everything to core editor :S
I will try it with the second option, I’m not sure that the first one is suitable for development (don’t know if the field numerical id will change). Thanks for the suggestion.