Should I use TDD and BDD if my project is changing fast?
I have my own little project I am creating using RoR, I plan it to have small-medium load.
With no doubt I started with BDD and TDD (Cucumber and RSpec to be exact, but I am also experienced with TestUnit), I like it but since it’s my own project and it’s a somewhat startup – I am changing many things in it, many requirements, many ideas how things should work and look. So it becomes too much time-consuming to always code it using BDD and TDD, even if I cover only common cases.
What should I do? Should I sacrifice BDD and TDD for productivity till I get to some point when I have a solid basis and it’s time for production, and than I write tests?
Should I write them right now but as minimal as possible? Should I only write RSpec and forget about Cucumber for now? Or maybe just TestUnit to test model for now since it’s the most important and everything else can change?
Thanks in advance!
Error in executing the maven plugin for Scala while running Diffy on macOS
Failed to execute goal net.alchim31.maven:scala-maven-plugin:4.5.4:compile (scala-compile-first) on project diffy: Execution scala-compile-first of goal net.alchim31.maven:scala-maven-plugin:4.5.4:compile failed.: CompileFailed -> [Help 1].
Should we be using actual environments to write integration Tests
I have been working as a Automation tester and my responsibility is to Create Integration automation tests. One of the questions I am having is should we use actual environment to write integration Tests. Example: If we have a consumer application that consumes from kafka and puts the message into MQ, we can write integration automation tests in multiple ways. I usually use test containers as my environments to write integration tests in these type scenario. However, I have seen people use actual Kafka and MQ environments to write integrarion tests. This could be isolated environments.