Testcase versioning explained

[chintans]

Objective - Teastcases change over time as the requirement changes or with addition of new requirements. It is critical to have a versioning system that can track these changes.

Explanation - All fields of testcase should have history except Test Results. Let's understand the whole requirement with an example.

• Sample Testcase(Version 1): User should be able to register using username, email and password
• Pre-Condition: User should not already be registered in system with same username or email address
• Steps:

1. Open the application in browser
2. Navigate to SignUp page by click on Signup button
3. Enter Username, email address and password
4. Click signup

• Test Data: Username: testuser Email - testuser@testing.com Password - P@ssw0rd

• Expected Result: Page is redirected to Account page

• Post Condition: User is created in system and active

---

• Sample Testcase(Version 2): User should be able to register using username, email and password
• Pre-Condition: User should not already be registered in system with same username or email address
• Steps:

1. Open the application in browser
2. Navigate to SignUp page by click on Signup button
3. Enter Username, email address and password
4. Click signup

• Test Data: Username: testuser Email - testuser@testing.com Password - P@ssw0rd

• Expected Result: User is redirected to activation message page. User will receive an email for activation

• Post Condition: User is created in system and but not active

---

Version history between version 2 and 1

• Expected Result: - Page is redirected to Account page + User is redirected to activation message page. User will receive an email for activation

• Post Condition: User is created in system and - active + but not active

---

• Sample Testcase(Version 3): User should be able to register using email and password
• Pre-Condition: User should not already be registered in system with same email address
• Steps:

1. Open the application in browser
2. Navigate to SignUp page by click on Signup button
3. Enter email address and password
4. Click signup

• Test Data: Email - testuser@testing.com Password - P@ssw0rd

• Expected Result: User is redirected to activation message page. User will receive an email for activation

• Post Condition: User is created in system and but not active

---

Difference between Version 3 and 2

• Title: User should be able to register using - username email and password
• Pre-Condition: User should not already be registered in system with same - username or email address
• Steps:

1. Open the application in browser
2. Navigate to SignUp page by click on Signup button
3. Enter - username, email address and password
4. Click signup

• Test Data: - Username: testuser Email - testuser@testing.com Password - P@ssw0rd

---

• Sample Testcase(Version 4): User should be able to register using email and password
• Pre-Condition: User should not already be registered in system with same email address
• Steps:

1. Open the application in browser
2. Navigate to Login page
3. Click on signup button on Login page
4. Enter email address and password
5. Click signup

• Test Data: Email - testuser@testing.com Password - P@ssw0rd

• Expected Result: User is redirected to activation message page. User will receive an email for activation

• Post Condition: User is created in system and but not active

---

Difference between Version 4 and 3

• Steps:

1. Open the application in browser - 2. Navigate to SignUp page by click on Signup button + 2. Navigate to Login page + 3. Click on signup button on Login page
2. Enter email address and password
3. Click signup

[Krunal-Promact]

I did few changes in models. So if we discuss your last scenario that you have said that if you add a test case as preconditions and after 2 days you remove it. so following things will happen in a database.

1) TestCaseConditions table will have one entry for adding test case as preconditions. 2) TestCaseConditionsVersion table will have one entry for versioning perspective.

after you remove that added test case. 1) IsDeleted flag will be set in TestCaseConditions. so we can find out that this record is deleted. 2) TestCaseConditionsVersion will have a new entry with existing value plus IsDeleted flag will be true. In order to identify that this record is now deleted.

[chintans]

Theoretically it looks ok, But I would need proper models to validate this.

[Krunal-Promact]

I did changes in models and pushed those changes as well. You can view that changes in PR. I have one question regarding versioning that does we have to maintain user info also that who did the changes in respective fields? Right now only changes along with date time are maintained in versioning.

[chintans]

Yes, We need to maintain who made the changes

[Krunal-Promact]

Ok. Will update the models accordingly and let you know.

[Krunal-Promact]

Models updated. Included who made the changes in respective tables. Please provide your feedback.