Add construction/destruction tests for the DEN matrix class

[KyleVaughn]

Description:

Develop a comprehensive set of unit tests to verify the correct construction and destruction of the DenseMatrix class. These tests will ensure that the DenseMatrix objects are properly initialized, can be copied and moved, and are correctly destroyed, maintaining the integrity of the dense matrix representation in our library.

Tasks:

• [ ] Create a new file named test_dense_matrix.cpp in the test directory.
• [ ] Set up the testing framework in the test file.
• [ ] Write test cases for the default constructor:
  • [ ] Verify that an empty matrix is created with 0 rows and 0 columns.
  • [ ] Check that the data vector is empty.
• [ ] Write test cases for the parameterized constructor:
  • [ ] Test creation of matrices with various dimensions (including edge cases like 0x0, 1x1, 10x1, 1x10, 10x10).
  • [ ] Verify that the dimensions are correctly set and the data vector has the correct size.
• [ ] Write test cases for the copy constructor:
  • [ ] Create a matrix, copy it, and verify that the copy has identical dimensions and data.
  • [ ] Modify the copy and ensure the original remains unchanged (deep copy verification).
• [ ] Write test cases for the move constructor:
  • [ ] Create a matrix, move it, and verify that the moved-to object has the correct state.
  • [ ] Check that the moved-from object is in a valid, empty state.
• [ ] Write test cases for the destructor:
  • [ ] Check for memory leaks.
  • [ ] If possible, implement a mock object or counter to verify that the destructor is called the expected number of times.
• [ ] Test edge cases and error handling:
  • [ ] Attempt to create matrices with negative dimensions and verify appropriate error handling.
  • [ ] Test with very large dimensions to check for any integer overflow issues.

Definition of done:

• Test cases implemented for default, parameterized, copy, and move constructors, and destructor
• Tests cover normal cases, edge cases, and error conditions
• All tests pass without memory leaks
• Test code is clean, well-commented, and integrated into the project's build system
• A brief summary of test coverage and results is provided

[kaleisss]

Very good job overall! You considered a lot of possible cases, such as memory leaks the correct invocation of the destructor. It is very nice that you also test for negative dimensions and very large matrices to improve robustness. However, for very large matrices, you might also want to ensure the tests assess performance and memory usage limits of the system.