refactor: [#227] rename tests in presentation test controllers

Renamed 6 test functions and 1 helper function in test controllers and reentrancy tests.

Tests: All tests pass

Author: josecelano

src/presentation/controllers/test/errors.rs

@@ -269,7 +269,7 @@ mod tests {
     use super::*;
 
     #[test]
-    fn test_invalid_environment_name_help_message() {
+    fn it_should_display_help_message_when_environment_name_is_invalid() {
         let error = TestSubcommandError::InvalidEnvironmentName {
             name: "invalid_name".to_string(),
             source: EnvironmentNameError::InvalidFormat {
@@ -286,7 +286,7 @@ mod tests {
     }
 
     #[test]
-    fn test_environment_not_found_help_message() {
+    fn it_should_display_help_message_when_environment_not_found() {
         let error = TestSubcommandError::EnvironmentNotFound {
             name: "test-env".to_string(),
             data_dir: "/path/to/data".to_string(),
@@ -299,7 +299,7 @@ mod tests {
     }
 
     #[test]
-    fn test_missing_instance_ip_help_message() {
+    fn it_should_display_help_message_when_instance_ip_is_missing() {
         let error = TestSubcommandError::MissingInstanceIp {
             name: "test-env".to_string(),
         };
@@ -310,7 +310,7 @@ mod tests {
     }
 
     #[test]
-    fn test_validation_failed_help_message() {
+    fn it_should_display_help_message_when_validation_fails() {
         let error = TestSubcommandError::ValidationFailed {
             name: "test-env".to_string(),
             source: Box::new(TestCommandHandlerError::MissingInstanceIp {

src/presentation/controllers/test/handler.rs

@@ -117,7 +117,7 @@ impl TestCommandController {
         let handler = self.create_command_handler()?;
 
         // 3. Execute validation workflow via application layer
-        self.test_infrastructure(&handler, &env_name).await?;
+        self.fixture_infrastructure(&handler, &env_name).await?;
 
         // 4. Complete workflow
         self.complete_workflow(environment_name)?;
@@ -176,7 +176,7 @@ impl TestCommandController {
     /// # Errors
     ///
     /// Returns `TestSubcommandError::ValidationFailed` if any validation check fails
-    async fn test_infrastructure(
+    async fn fixture_infrastructure(
         &mut self,
         handler: &TestCommandHandler,
         env_name: &EnvironmentName,

src/presentation/tests/reentrancy_fix_test.rs

@@ -14,7 +14,7 @@ use crate::presentation::views::{UserOutput, VerbosityLevel};
 /// 3. With `std::sync::Mutex`, this would deadlock because same thread tries to acquire twice
 /// 4. With `ReentrantMutex`, this should work fine
 #[test]
-fn test_reentrancy_deadlock_fix_issue_164() {
+fn it_should_not_deadlock_when_nested_user_output_calls_occur() {
     // Create a UserOutput wrapped in ReentrantMutex<RefCell<>> pattern
     let user_output = Arc::new(ReentrantMutex::new(RefCell::new(UserOutput::new(
         VerbosityLevel::Silent,
@@ -53,7 +53,7 @@ fn test_reentrancy_deadlock_fix_issue_164() {
 
 /// More comprehensive test that simulates the exact deadlock scenario from production
 #[test]
-fn test_comprehensive_reentrancy_scenario() {
+fn it_should_handle_complex_nested_output_when_testing_reentrancy() {
     let user_output = Arc::new(ReentrantMutex::new(RefCell::new(UserOutput::new(
         VerbosityLevel::Silent,
     ))));