ogma VS testing-nestjs

[1] https://github.com/nasa/ogma

The changelog is available at: https://github.com/nasa/ogma/releases/tag/v1.0.8

https://space-ros.github.io/docs/rolling/Related-Projects/Ogma.html https://github.com/nasa/ogma

For more details, including videos of monitors being generated and flown in simulators, see: https://github.com/nasa/ogma

The student, if selected, will be working on extending our capabilities to test cFS/ROS/FPrime applications, especially those using Ogma and/or Copilot for monitoring. Both Ogma and Copilot are open-source software written in Haskell.

Among others, Copilot has been used at the Safety Critical Avionics Systems Branch of NASA Langley Research Center for monitoring test flights of drones. It also serves as a runtime monitoring backend for the requirements elicitation tool FRET (https://github.com/NASA-SW-VnV/fret/), via Ogma (https://github.com/nasa/ogma).

Understanding these properties can get hard. Using a high level language as opposed to just C is very helpful (we review the code of flight systems with sometimes 4-5 people in the room and it's not trivial at all what it is doing or to show that it is correct). But even streams can sometimes be hard to understand for very complex monitors. We've also built Ogma (https://github.com/nasa/ogma) so that people can write properties in structured natural language, or transform other languages into Copilot (and then C/whatever).

NASA Ogma: generate hard-realtime C runtime monitoring applications\ (0 comments)

To echo the other's here, Nx has been an amazing dev experience for me! I use it for ogma, for nest-commander, testing-nestjs, and for nest-samples and @nest-lab/, all using pnpm as a package manager.

The prisma sample app in the testing-nestjs repository does a great job on showing how to do testing a NestJS app with Prisma.

Example https://github.com/jmcdo29/testing-nestjs/blob/8519ae7043d1dde5ae12a5d8f8ab02ea3c3c2fcf/apps/complex-sample/src/cat/cat.interceptor.spec.ts

Question: for your e2e tests will you be using something like supertestto send the gql request? And if so, could I suggest you look at pactum which (in my opinion) has a stronger API and better gql support. I've got an example here if you need it

Test files usually shouldn't be too large. You should just need a simple mock for each injected dependency for the service. You can see a lot of examples I have here. If you could show your test file it may help us figure out why it might be really large.

Then there's also a @nestjs/testing package that can be used for overriding these injections during tests to make for super easy unit testing (in my opinion) and a large repo of examples here.