feat: update examples to use gpt-4o-mini

Author: jungs1

README.md

@@ -19,7 +19,6 @@ Check it out here: [Roadmap](https://github.com/codeintegrity-ai/mutahunter/issu
 
 We'd love to hear your feedback, suggestions, and any thoughts you have on mutation testing. Join the discussion and share your insights on the roadmap or any other ideas you have. 🙌
 
-
 ## Table of Contents
 
 - [Features](#features)

examples/go_webservice/README.md

@@ -19,19 +19,34 @@ gocov convert coverage.out | gocov-xml > coverage.xml
 Currently test coverage is 96.6%. Let's see what the mutation coverage is.
 
 ```bash
-# --extreme flag is used to run the mutation testing in extreme mode. This does not use the LLM-based model.
-mutahunter run --test-command "go test" --code-coverage-report-path "coverage.xml" --only-mutate-file-paths "app.go" --extreme
-
-# After achieving a high mutation score, let's say 90%, you can check one last time using LLM-based
-
-# go seems to do pretty bad when using gpt-3.5-turbo, so we recommend using gpt-4o
-
 export OPENAI_API_KEY=your-key-goes-here
 
-mutahunter run --test-command "go test" --code-coverage-report-path "coverage.xml" --only-mutate-file-paths "app.go" --model "gpt-4o"
-
-## you can use --modifies-files-only to only mutate the files that are modified by the test suite
-mutahunter run --test-command "go test" --code-coverage-report-path "coverage.xml" --only-mutate-file-paths "app.go" --extreme --modifies-files-only
+mutahunter run --test-command "go test" --code-coverage-report-path "coverage.xml" --only-mutate-file-paths "app.go" --model "gpt-4o-mini"
+```
 
-## and then keeping improving the test suite until you get 100%
+```bash
+2024-07-18 16:13:56,632 INFO: 📊 Overall Mutation Coverage 📊
+📈 Line Coverage: 97.00% 📈
+🎯 Mutation Coverage: 52.63% 🎯
+🦠 Total Mutants: 21 🦠
+🛡️ Survived Mutants: 9 🛡️
+🗡️ Killed Mutants: 10 🗡️
+🕒 Timeout Mutants: 0 🕒
+🔥 Compile Error Mutants: 2 🔥
+💰 Expected Cost: $0.00579 USD 💰
+2024-07-18 16:13:56,632 INFO: 📂 Detailed Mutation Coverage 📂
+📂 Source File: app.go 📂
+🎯 Mutation Coverage: 52.63% 🎯
+🦠 Total Mutants: 21 🦠
+🛡️ Survived Mutants: 9 🛡️
+🗡️ Killed Mutants: 10 🗡️
+🕒 Timeout Mutants: 0 🕒
+🔥 Compile Error Mutants: 2 🔥
+
+2024-07-18 16:13:59,928 INFO: Mutation Testing Ended. Took 121s
 ```
+
+### Surviving Mutant Analysis
+
+[Mutants](./mutants.json)
+[Report](./mutant_analysis.md)

examples/go_webservice/mutant_analysis.md

@@ -0,0 +1,27 @@
+### Vulnerable Code Areas
+**File:** `app.go`  
+**Location:** Multiple functions including `subtractHandler`, `multiplyHandler`, `isPalindromeHandler`, `daysUntilNewYearHandler`, and `echoHandler`.  
+**Description:** The surviving mutants indicate that the code lacks robust error handling for parameter conversions and edge cases, such as empty inputs and boundary conditions. For instance, the `subtractHandler` does not handle conversion errors, and the `multiplyHandler` incorrectly returns 0 when either number is 0 without proper context.
+
+### Test Case Gaps
+**File:** `app_test.go` (assumed)  
+**Location:** Various test methods for arithmetic operations and string manipulations.  
+**Reason:** Existing test cases likely do not cover scenarios such as:
+- Invalid or empty parameters (e.g., `subtractHandler` and `echoHandler`).
+- Edge cases like multiplying by zero or checking for palindromes with empty strings.
+- Leap year considerations in `daysUntilNewYearHandler`.
+
+### Improvement Recommendations
+**New Test Cases Needed:**
+1. **Test Method:** `testSubtractHandlerInvalidInput`
+   - **Description:** Validate behavior when non-integer inputs are provided.
+2. **Test Method:** `testMultiplyHandlerZeroInput`
+   - **Description:** Ensure that multiplication by zero is handled correctly and returns a meaningful response.
+3. **Test Method:** `testIsPalindromeHandlerEmptyString`
+   - **Description:** Check the response when an empty string is passed to the palindrome check.
+4. **Test Method:** `testDaysUntilNewYearHandlerLeapYear`
+   - **Description:** Test the calculation of days until New Year during a leap year to ensure accuracy.
+5. **Test Method:** `testEchoHandlerEmptyMessage`
+   - **Description:** Validate the response when an empty message is provided, ensuring proper error handling.
+
+By addressing these gaps, the robustness of the application can be significantly improved, ensuring better handling of edge cases and invalid inputs.

examples/java_maven/mutant_analysis.md

@@ -0,0 +1,25 @@
+### Vulnerable Code Areas
+**File:** `src/main/java/com/example/BankAccount.java`  
+**Location:** Lines 28, 36, 39, 66  
+**Description:** The methods `deposit` and `withdraw` do not handle zero or negative amounts correctly. Specifically, the `withdraw` method ignores the overdraft limit if the withdrawal amount is less than the balance. Additionally, the `scheduleTransaction` method allows for scheduling transactions with zero days, which could lead to unintended immediate execution.
+
+### Test Case Gaps
+**File:** `src/test/java/com/example/BankAccountTest.java`  
+**Location:** Test methods `testDeposit`, `testWithdraw`, and `testScheduleTransaction`  
+**Reason:** Existing test cases do not account for edge cases such as zero or negative deposit/withdrawal amounts. The tests also fail to validate the behavior when overdraft limits are ignored or when scheduling transactions for zero days.
+
+### Improvement Recommendations
+**New Test Cases Needed:**
+1. **Test Method:** `testDepositZeroOrNegativeAmount`
+   - **Description:** Verify that depositing zero or negative amounts throws an `IllegalArgumentException`.
+   
+2. **Test Method:** `testWithdrawZeroOrNegativeAmount`
+   - **Description:** Ensure that attempting to withdraw zero or negative amounts results in an `IllegalArgumentException`.
+
+3. **Test Method:** `testWithdrawExceedingBalanceIgnoringOverdraft`
+   - **Description:** Test the scenario where a withdrawal exceeds the balance but is within the overdraft limit to confirm proper handling.
+
+4. **Test Method:** `testScheduleTransactionZeroDays`
+   - **Description:** Validate that scheduling a transaction for zero days raises an `IllegalArgumentException`.
+
+By addressing these gaps, the test suite will better cover critical edge cases, enhancing the robustness of the `BankAccount` class.