Open StaticRocket opened 5 years ago
Automated tests are always a goo idea. Some of the tests seem to be wrong at first glance, as it expects e.g. the element to not exist when it actually has display:none;
Alright, awesome. I'll poke around and see what I can figure out. I just wanted to see if this was something you'd be interested in, especially considering you ultimately control those integration settings. I'll leave this thread open in case any other questions regarding this come up.
@Sorunome sorry for the silence. I've gotten dragged in a completely different direction by a number of things. Atom fell back on Electron4 (going against my rolling release mentality and pushing me to Neovim, a tool I had been using for quite some time now) and I've started playing with FPGAs, Assembly, Java, Machine Learning, and SysAdmin stuff to boot. I still intend on helping out wherever possible but this project is currently on the back-burner as I keep getting thrown stray projects at college.
One idea I had been working on for a revamp (to address several issues all at once) was to dump the Arduino IDE dependency and board selection stuff and just add hooks for Arduino-Makefile support. It would be a little jarring for current users but way faster and make board support and selection way cleaner. Just a thought. Best of luck with this project, dude.
I'm looking at trying to get the /spec directory and some configs sorted out so we could potentially use Travis CI and GreenKeeper to try to limit issue sources. @Sorunome, do you think this is worth perusing? Right now (working in my fork), I've found that arduino-upload-view-spec.coffee introduces an impossible test, so I've removed. but arduino-upload-spec.coffee throws a few errors as well.
~$ apm test