diff --git a/tests/testcases/Group1-user-management/1-01-DB-user-registration.md b/tests/testcases/Group1-user-management/1-01-DB-user-registration.md
index e5359baba..078849afd 100644
--- a/tests/testcases/Group1-user-management/1-01-DB-user-registration.md
+++ b/tests/testcases/Group1-user-management/1-01-DB-user-registration.md
@@ -19,8 +19,8 @@ User guide
 3. Use the username of the newly registered user to log in to the UI.
 4. Log out from the UI.
 5. Use the email of the newly registered user to log in to the UI.
-5. On a Docker client host, use `docker login <harbor_host>` command to verify the user can log in by either the **username** or **email** . (verify both) 
-6. Log out from the UI and register another new user. Try to provide invalid values of input to see if validation works: 
+6. On a Docker client host, use `docker login <harbor_host>` command to verify the user can log in by either the **username** or **email** . (verify both) 
+7. Log out from the UI and register another new user. Try to provide invalid values of input to see if validation works: 
 
 
 * username is the same as an existing user
diff --git a/tests/testcases/Group2-image-management/2-06-DB-user-delete-projects.md b/tests/testcases/Group2-image-management/2-06-DB-user-delete-projects.md
index 72b3508a5..1f8b7c954 100644
--- a/tests/testcases/Group2-image-management/2-06-DB-user-delete-projects.md
+++ b/tests/testcases/Group2-image-management/2-06-DB-user-delete-projects.md
@@ -19,7 +19,7 @@ User guide
 **NOTE:**  
 * In below test, user A is non-admin user. User A and project X should be replaced by longer and meaningful names.
 * Must use two kinds of browsers at the same time to ensure independent sessions. For example, use Chrome and Firefox, or Chrome and Safari. 
-* DO NOT use the same browser to log in two users in different windows(tabs).
+* DO NOT use the same browser to log in two users at the same time in different windows(tabs).
 
 1. Log in to UI as user A (non-admin).
 2. Create a project X so that the user has the project admin role.
diff --git a/tests/testcases/Group2-image-management/2-12-LDAP-user-push-multiple-images.md b/tests/testcases/Group2-image-management/2-12-LDAP-user-push-multiple-images.md
index 2a861389e..a7f845b65 100644
--- a/tests/testcases/Group2-image-management/2-12-LDAP-user-push-multiple-images.md
+++ b/tests/testcases/Group2-image-management/2-12-LDAP-user-push-multiple-images.md
@@ -3,7 +3,7 @@ Test 2-12 - User Push Multiple Images (LDAP Mode)
 
 # Purpose:
 
-To verify that a non-admin user can push multiple images to a project in (LDAP mode).
+To verify that a non-admin user can push multiple images to a project in LDAP mode.
 
 # References:
 User guide
diff --git a/tests/testcases/Group2-image-management/2-13-LDAP-user-push-multiple-projects.md b/tests/testcases/Group2-image-management/2-13-LDAP-user-push-multiple-projects.md
index 45de75269..268baa422 100644
--- a/tests/testcases/Group2-image-management/2-13-LDAP-user-push-multiple-projects.md
+++ b/tests/testcases/Group2-image-management/2-13-LDAP-user-push-multiple-projects.md
@@ -3,7 +3,7 @@ Test 2-13 - User Create Multiple Projects (LDAP Mode)
 
 # Purpose:
 
-To verify that a non-admin user can create multiple projects in (LDAP mode).
+To verify that a non-admin user can create multiple projects in LDAP mode.
 
 # References:
 User guide
diff --git a/tests/testcases/Group4-logging/4-01-DB-user-view-logs.md b/tests/testcases/Group4-logging/4-01-DB-user-view-logs.md
new file mode 100644
index 000000000..935a91081
--- /dev/null
+++ b/tests/testcases/Group4-logging/4-01-DB-user-view-logs.md
@@ -0,0 +1,39 @@
+Test 4-01 - User Views Logs (DB Mode)
+=======
+
+# Purpose:
+
+To verify that a non-admin user can views logs when users are managed locally by Harbor (DB mode).
+
+# References:
+User guide
+
+# Environment:
+* This test requires that a Harbor instance is running and available.
+* Harbor is set to authenticate against a local database. ( auth_mode is set to **db_auth** .) The user data is stored in a local database.
+* A linux host with Docker CLI installed (Docker client).
+
+# Test Steps:
+1. On a Docker client host, use `docker login <harbor_host>` command to log in as a non-admin user. 
+2. Run some `docker push` and `docker pull` commands to push images to the registry and pull from the registry.
+3. Log in to the UI as the non-admin user.
+4. Delete a few images from the project. 
+5. View the logs of the project. 
+6. Try below search criteria to see if the search result is correct:
+
+* push only
+* pull only
+* pull and push
+* delete only
+* all
+* push and delete
+* different date ranges 
+* date range and push
+
+# Expected Outcome:
+* All operations in Step 2 & 4 should be logged.
+* Logs can be viewed in Step 5, check if the time and operations are correct.
+* Logs can be filtered in Step 6.
+
+# Possible Problems:
+None
\ No newline at end of file
diff --git a/tests/testcases/Group4-logging/4-01-DB-user-view-logs.md.bak b/tests/testcases/Group4-logging/4-01-DB-user-view-logs.md.bak
new file mode 100644
index 000000000..0566fad00
--- /dev/null
+++ b/tests/testcases/Group4-logging/4-01-DB-user-view-logs.md.bak
@@ -0,0 +1,37 @@
+Test 4-01 - User Views Logs (DB Mode)
+=======
+
+# Purpose:
+
+To verify that a non-admin user can views logs when users are managed locally by Harbor (DB mode).
+
+# References:
+User guide
+
+# Environment:
+* This test requires that a Harbor instance is running and available.
+* Harbor is set to authenticate against a local database. ( auth_mode is set to **db_auth** .) The user data is stored in a local database.
+* A linux host with Docker CLI installed (Docker client).
+
+# Test Steps:
+1. On a Docker client host, use `docker login <harbor_host>` command to log in as a non-admin user. 
+2. Run some `docker push` and `docker pull` commands to push images to the registry and pull from the registry.
+3. Log in to the UI as the non-admin user.
+4. Delete a few images from the project. 
+5. View the logs of the project. 
+6. Try below search criteria to see if the search result is correct:
+
+* push only
+* pull only
+* pull and push
+* delete only
+* all
+* push and delete
+
+# Expected Outcome:
+* All operations in Step 2 & 4 should be logged.
+* Logs can be viewed in Step 5, check if the time and operations are correct.
+* Logs can be filtered in Step 6.
+
+# Possible Problems:
+None
\ No newline at end of file