Ok. Gonna migrate this topic to new thread. Sounds like this could take a few different form factors, but worth exploring!
> On Mar 15, 2021, at 12:28 PM, Austin Bennett <[email protected]> > wrote: > > In general more testing == better (at least until extreme). > > Glad for that topic to be pushed. And, welcome, @Gedd! > > (from someone that mostly lurks/follows the community, rather than doing > much by way of actually contributing thus far!). > > > > On Mon, Mar 15, 2021 at 8:35 AM Rob Foley <[email protected]> wrote: > >> Sounds reasonable to me. There might be some tricky bits regarding >> certain mouse events, since Cypress doesn't let you do things like >> "hover", for example, without writing some vaguely hacky jQuery. Overall >> sounds helpful though. >> >> Rob >> >> On 3/15/2021 9:40 AM, Joshua Poore wrote: >>> Rob! >>> >>> What’s up!? >>> >>> I see where you’re coming from on Cypress—UserALEjs is not a user facing >> app. However, @UncleGedd is the second current or frmr user to think >> Cypress is a good idea. For my part, I see two possible, but not mutually >> exclusive benefits: >>> >>> 1. The user community Gedd is coming from rely more on UserALEjs’s >> custom logging and filtering capabilities than they do the ‘raw” log >> stream. Being careful with words: users are developers working with >> UserALEjs in their projects and/or data scientists analyzing UserALEjs >> data. Unit tests can/do flex aspects of our exports/API, but better testing >> will involve more sophisticated usage of custom logs, mapping statements, >> filters and option params. If Cypress proves to be an easy and efficient >> way of automating the integration tests I do with say our ./example >> index.html, I think it’s worth considering. Else we can think of beefing up >> unit tests. >>> >>> 2. Even if we don’t do a “full tilt” Cypress integration for UserALEjs, >> it would probably be useful to put together some examples somewhere and >> maybe do a screen-cap movie of how people can include userale payloads in >> their own apps Cypress testing. Especially, those that do a lot of >> filtering, mapping, and custom logging, it might be nice to provide tips >> and know-how for how to validate which logs are being produced, whether >> they have the desired structure, and whether their values are in the right >> format. Code coverage in testing is important for a lot of organizations, I >> think we would do well by users to scaffold them a bit in helping them test >> the code they are adding to support logging. >>> >>> I’m willing to see what kinds of examples we get for Cypress and raise >> for discussion how deeply or how we consider integrating them into the >> project. Sound reasonable? We can continue discussion on another thread. >>> >>> Josh >>> >>>> On Mar 14, 2021, at 1:09 PM, Rob Foley <[email protected]> wrote: >>>> >>>> Hi Gedd, >>>> >>>> Thanks for contributing. If you have any questions about Userale or any >> of its design decisions, feel free to reach out. Ditto on the Zoom/etc. >> front. >>>> >>>> @poorejc wrt Cypress, I've gotten a decent bit of experience writing >> Cypress tests in the last year or so. I don't quite see (at first) how it >> fits into Flagon-land. Can you tell me a bit more about that (another >> thread is fine). >>>> >>>> Regards, >>>> Rob >>>> >>>> On 3/13/2021 8:57 PM, Joshua Poore wrote: >>>>> Hi Gedd, >>>>> >>>>> Thanks again for the great contributions! We are always looking for >> new committers, especially those that were (are) users! Very familiar with >> the Kessel Run crowd. Maybe over a zoom or coffee we can catch up about >> that. >>>>> >>>>> I’ve added a few new tickets in our Journey Tests project. Over the >> next week, I’ll be digging into Cypress (seems what users want to do, and >> you!) and doing a little bug-hunting. >>>>> >>>>> Flagon is a great place to start your exploration of open-source—we’re >> a small community, and we’re just about to start a major refactor on our >> key analytical product (distill) to support python data pipelines with >> useralejs data. We might even explore Apache Superset integration. We’re >> also discussing graduation from the Apache Incubator, meaning that we would >> graduate as or to a top level project. So, it’s a really interesting >> project and time in that projects’ history to be involved. You can see how >> things are done at Apache and perhaps become an apache committer/member and >> get involved in a variety of projects. Some of our mentors for examples >> have had illustrious careers on projects like Solr and Tika. Good entry >> point for lots of interesting madness :) >>>>> >>>>> poorejc >>>>> >>>>>> On Mar 13, 2021, at 11:57 AM, Gedd Johnson <[email protected]> >> wrote: >>>>>> >>>>>> Hello! >>>>>> >>>>>> My name is Gedd Johnson (UncleGedd <https://github.com/UncleGedd> on >>>>>> Github). I am currently a military officer working with a group called >>>>>> Kessel Run. My previous team and I forked the Userale repo and made a >>>>>> couple mods to fit our needs at the time. Since then, I have moved on >> to >>>>>> other endeavors but wanted to get involved in the open source >> community; I >>>>>> thought the Flagon project would be a good place to start. >>>>>> >>>>>> I'm actually on my way out of the military and have ample time to >> spare at >>>>>> the moment, so I'm happy to contribute as much as I'm able. Feel free >> to >>>>>> connect with me on LinkedIn >>>>>> <https://www.linkedin.com/in/gedd-johnson-9bb009148/>, and I'm happy >> to do >>>>>> coffee over Zoom/Hangouts/etc. >>>>>> >>>>>> Nice to meet you! >>>>>> Gedd Johnson >>
