Scribd
Upload
43 views9 pages

ManageEngine Test Strategy & Plan

The test strategy document outlines a plan to test the incident creation functionality in ManageEngine ServiceDesk through Splunk. Key areas to be tested include creating incidents, validating incident details, assigning correct categories and priorities, and confirmation of creation. Automated testing will focus on validating an incident ticket is correctly generated from an alert in Splunk and required fields like priority and use case are populated based on rules. The testing is scheduled to take place from November 26th to the 26th in the production environment, with the expected deliverable being confirmation that incident creation through Splunk functions properly.

Uploaded by

nasim.snow2022
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
43 views9 pages

ManageEngine Test Strategy & Plan

The test strategy document outlines a plan to test the incident creation functionality in ManageEngine ServiceDesk through Splunk. Key areas to be tested include creating incidents, validating incident details, assigning correct categories and priorities, and confirmation of creation. Automated testing will focus on validating an incident ticket is correctly generated from an alert in Splunk and required fields like priority and use case are populated based on rules. The testing is scheduled to take place from November 26th to the 26th in the production environment, with the expected deliverable being confirmation that incident creation through Splunk functions properly.

Uploaded by

nasim.snow2022
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 1/9

TEST STRATEGY / PLAN

This document is the property of Hamad International Airport. This document contains
information that is confidential and proprietary to HIA. In consideration of receipt of this
document, the recipient agrees to maintain such information in confidence and not to
reproduce or otherwise disclose this information to any person without prior written
approval from HIA. This document will remain under strict electronic control by HIA. HIA
reserves the right to, upon request, receives back any printed copies of this document or
to request confirmation that any electronic copies have been destroyed.

Scope Sign-Off

Name & Designation Signature Date

Mohammad Nasim – ITSM Engineer


26-11-2023

1
Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 2/9

Distribution List
Name Designation Role

Version History

Version Description Status Author Date

1.0 Incident Creation in ManageEngine Draft Mohammad Nasim 26-11-2023


ServiceDesk through Splunk

2
Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 3/9

Table of Contents

1. INTRODUCTION....................................................................................................................................................................................4
2. TESTING OBJECTIVES........................................................................................................................................................................4
3. TESTING SCOPE....................................................................................................................................................................................4
4. FEATURES TO BE TESTED.................................................................................................................................................................4
5. TEST ENVIRONMENT..........................................................................................................................................................................4
6. TEST PROCESS......................................................................................................................................................................................5
7. TESTING TOOLS...................................................................................................................................................................................7
8. TEST SCHEDULE...................................................................................................................................................................................8
9. TEST DELIVERABLES.........................................................................................................................................................................8

3
Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 4/9

1. Introduction

The purpose of this test plan is to ensure the effective testing of ManageEngine ServiceDesk Plus to
guarantee its reliability, performance, and functionality.

2. Testing Objectives

The primary objective of this test plan is to ensure that the incident creation functionality performs
accurately, efficiently, and in accordance with the specified requirements.

3. Testing Scope

The test will focus on validating the incident creation process within the ManageEngine ServiceDesk
Plus.

4
Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 5/9

4. Features To Be Tested

 Creating a new incident.


 Validating incident details
 Assigning incident to the correct category and priority
 Notification and confirmation of incident creation

5. Test Environment

 Production Environment

6. Test Process

 Incident creation in ManageEngine ServiceDesk via Splunk

Upon the detection of an alert in Splunk, an automated email is generated and sent to the designated mailbox.
Subsequently, the mailbox forwards the email to ManageEngine, where an Incident ticket is created.

For example –

The below Incident “Request ID:11302” has been generated in ManageEngine ServiceDesk through Splunk
using the default template.

5
Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 6/9

 Validation for Fields –

As per subject line – Automatically Priority & UseCase fields values set based on business rule validation.

We have created the business rule validation for Priority & UseCase for Incident.

 Priority Validation – For Priority 3

6
Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 7/9

 UseCase Validation – For “G003-Disc-Network Share Discovery Traffic Detected

For this incident “Request ID:11302”, the priority is 3, so a Priority 3 SLA has been attached to the ticket.

7
Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 8/9

We can check the SLA details in Time Analysis tab -

 Service Level Agreements (SLAs) – SOC

These Service Level Agreements (SLAs) have been specifically configured to address and manage Security
Operations Center (SOC) incidents effectively.

7. Testing Tools

8
Project Title: Test Strategy / Plan

Project Ref. No.: Version No.: 1.0 Version Date: 26/11/2023 Page: 9/9

8. Test Schedule

Test Start Date - 26/11/2023 : Test End date – 26/11/2023

9. Test Deliverables

As per the above incident creation through Splunk, all validations are working fine as expected.

You might also like