Unveiling WLSDM Version-4: A Journey Through Software Release Testing with JDK 11
From Code to Launch: The Testing Process of WLSDM Version-4 with JDK 11
In the dynamic world of software development, ensuring that every component functions seamlessly is paramount. End-to-end testing of JDK 11 plays a crucial role in this process, providing a thorough validation of its functionality, performance, and reliability. By meticulously evaluating each aspect, we guarantee that JDK 11 meets the highest standards of excellence and readiness for deployment. Join us as we delve into the comprehensive testing journey of WLSDM Version-4, showcasing the meticulous process and robust outcomes achieved with JDK 11.
Environment List
• Java Version: java 11.0.21 2023–10–17 LTS
• WebLogic Server Version: 14.1.1.0.0
• WLSDM Version: v4.1.1-b5066
• JavaServerLoader
• TechCo-ECommerce-1.0-SNAPSHOT
The Purpose of Testing
The testing encompasses end-to-end tests for the integration of JDK 11 with WLSDM.
The Roadmap Followed During Testing
In order to conduct backend tests, the JavaServerLoader and TechCo-Ecommerce applications were deployed on WebLogic 14. WLSDM threshold values were adjusted to their minimum values to capture all events occurring in the backend. To capture backend events, “New Back-end System Monitoring” was added from the Add/Update Monitoring & Diagnostics Configurations page.
Back-end Tests
To stress the system, the CPU Performance test was initiated via the JavaServerLoader application. Subsequently, the CheckOut function with a sleep function in the TechCo-Ecommerce application was executed to create load on the backend. Each page related to the backend was individually checked through WLSDM to demonstrate successful data collection. The checked pages are as follows:
1- Back-end Systems→ Back-end Generic
- It was observed that JDBC and EJB event information was successfully collected and listed in the table on the BACK-END GENERIC page.
2- Back-end Systems → JDBC
- Relevant event tables were successfully created on the JDBC page.
3- Back-end Systems → EJB
- The relevant event tables were successfully created on the JDBC page.
4- Back-end Systems → HTTPClient Outbound Call
5- Socket I/O
6- Transaction Profiling and Slow Traces
- The sleep function executed on the TRANSACTION PROFILING AND SLOW TRACES page was successfully displayed in the table. Clicking on it provided the transition to the relevant detail section where details related to the function were listed.
7- Notifications → Metric Notifications
- Load was generated on the CPU via the JavaServerLoader tool in the Metric Notifications section, and the load generated here was listed in detail on the page. When the load test ended, the relevant clear notification appeared in the table.
8- Reports → Metric Reports
- The details of the relevant metrics resulting from the load tests could be tracked under the “Metric Reports” page.
9- Reports → Back-end Reports
- After setting the relevant filters on the Back-end Reports page, daily reports were successfully listed using the “Get Report From Daily Data” button. However, it was observed that the “Get Report” button did not work when attempting to fetch a report from a specific time period.
- The “Get Report” button is not functioning as expected.
UPDATE: It was learned that the “Get Report” button retrieves only data with the store feature enabled from metric settings. The button is functioning successfully.
10- Reports → Back-end Systems Top Events
11- Reports → Response Times Top Requests
List Of Pages Containing JFR (Java Flight Recording)
- In the Smart Dashboards → JVM System Resources page, the “Actions” buttons in the tables contain JFR.
2. In the Smart Dashboards → Servers page, the “Actions” buttons in the tables contain JFR.
3. In the Monitoring & Diagnostics → Profiling Dumps page, there are tables under the “Profiling Dumps” and “Flight Recorder Repository (Auto JFRs)” tabs that allow us to generate manual JFR files or automatically generate JFR files.
4. Under Configuration → WLSDM System Settings page, the following JFR parameter settings are found in the “system.monitoring” table:
- system.monitoring.metric.actions.jfr.default.settings
- system.monitoring.metric.actions.jfr.duration
Transaction Profiling and Slow Traces
Backend Dashboard
A dashboard named “Test” has been created from the Add Monitoring page. Events were added to this dashboard under the Back-end System category. It was observed that the events were successfully listed.
View WLSDM Agent
- A dashboard named “Test” has been created from the Add Monitoring page. Events were added to this dashboard under the Back-end System category. It was observed that the events were successfully listed.
WLSDM Extended Monitoring and Outbound URL Monitoring
- A Network Socket test was performed using the JavaServerLoader tool. The test results were successfully listed under Outbound Call in the Back-end Reports section.
UI Tests
- UI tests were conducted across three different web browsers. During the test, significant issues were not encountered. However, one bug was identified, and I have two suggestions for improvement that I propose.
INTERNET BROWSERS USED IN THE TEST
- Opera
- Chrome
- Mozilla
IDENTIFIED UI BUGS
- If the WLSDM Navigation Bar is pinned by clicking on it and the Bar is enlarged downwards, the “Configuration” tab is positioned below the Volthread logo.
SUGGESTED IMPROVEMENTS
1. In the Back-end Monitoring detail page, when clicking on the Root Cause button to open the pages, it is difficult to read because the height of the “Event Thread” table is too short.
2. To close opened pop-ups, it is mandatory to click on the Close or “X” button. It could be more convenient if they could also be closed by clicking on an empty area of the page.
3. As the Navigation Bar grows in size, it requires scrolling down the entire page to access the buttons at the bottom. I believe that if the bar is fixed and a structure is designed to only move the bar downwards, the page layout would look more aesthetically pleasing.
Installation
- A clean installation of WLSDM has been successfully completed without encountering any errors.
Overall Test Results of WLSDM Version-4 Release
The tests have been largely completed successfully. No errors have been encountered on the back-end. During the UI tests, one bug was identified that does not affect the system’s functionality.
Suggestions for improvement, which I find beneficial, have been mentioned in the relevant area.
Author: Ozgun Deniz Bedel | Volthread
Co-Authors: Can Sahin | Volthread, Fevzi Korkutata | Volthread
