A Test Plan Update

Greetings, fellow software enthusiasts! Today, we’ll be discussing the progress of our software project, RALF.

Demo Update

First, let’s talk about the recent updates to our demo. Our team has been working tirelessly to improve the frontend, creating new pages and designs for the flow creation process you can see in the following image. We’ve also been polishing the engine, making it more user-friendly for the regex-replace action.

New Flow Creation Page Designs in the Works 👀

But, wait! There’s more! We’ve also been putting the finishing touches on “today”, the RALF companion for the CLI. The tool now allows for custom formats via templating, so you can tailor it to your heart’s content. It’s like having your cake and eating it too, but in the form of a CLI tool 🎂.

$ today show --ralf definition.yaml --template '{{ .Summary }} {{ .RelativeRAW }}'

This allows for fun custom prompts, you can even go crazy and try this out:

while true
do 
  clear
  echo '\n\n\n\n\n\n\n\n'
  today show --ralf definition.yaml --template '{{.RelativeRAW}}' | figlet -c -f contrast | sed 's/%/█/g' | sed 's/[\.\s]/:/g' | lolcat -a -s 100
  echo -n "remaining" | figlet -c | lolcat -a -s 100
  sleep 5
done

Test Plan

Moving on to the test plan, let’s dive into the different types of tests we’ve planned for our beloved RALF. We’ve got a smorgasbord of tests lined up, including: Unit Testing (for the engine and backend), API-Testing (for the engine and backend) and DOM-Testing (for the frontend).

Get RALF P’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Now, let’s talk numbers. What’s our target test coverage, you ask?

• Engine: Shooting for the stars with >80%
• Backend: Aiming high at >50%
• Frontend: A modest >20%, but hey, progress is progress!

We know what you’re thinking: “But, what tools will you use for these fantastic tests?” Fear not, dear reader, for we have answers:

• Engine: The trusty testing package (standard library, tried and true)
• Backend: Spring Testing (because it’s always springtime in RALF’s world)
• Frontend: react-testing-library (because we want to treat RALF’s UI with the utmost care)

We’ll be running all unit tests in a GitHub Pipeline. This allows us to see which commit (and version) breaks which part of the software. It’s like having a crystal ball 🔮 that shows you exactly where things went off the rails, but instead of a ball, it’s a GitHub Pipeline, and instead of rails, it’s RALF. You get the idea.

In Conclusion

So there you have it, folks! We’ve covered the progress of our demo, the test plan, and the tools we’ll be using. We hope you enjoyed this update on our dear friend RALF. As we continue to develop RALF, we promise to keep you in the loop, sharing more updates, and maybe even a few magic tricks (no promises on that last one, though).

“All we have to decide is what to do with the time that is given to us… and make sure RALF works flawlessly!” ~ Gandalf the Grey (but not so grey)