Lessons Learned from a Multi‑Module Java/Node.js Project: Improving Communication, Testing Practices, and Pre‑Production Validation

The author participated in a seven‑module system project developed with Java and Node.js over five months, involving around ten developers (including outsourced staff) and a rotating testing team.

Insufficient Communication with the Project Manager

The test account provided to the client for pre‑production was mistakenly the same as the one used in the test environment.

The project manager did not inform the team to conduct internal pre‑production testing before client hand‑over.

Testing Process Not Properly Enforced

Pre‑production validation was omitted; after passing tests in the test environment, no regression testing was performed with business users in pre‑production, leading to bugs such as empty Excel exports and permission configuration errors.

Due to a tester’s sick leave, pre‑production (including account permissions) was released to production without confirmation testing.

Functional Defects

Missing validation for start‑date and end‑date relationships.

Missing validation for taxable versus non‑taxable amount relationships.

Text fields allowed overly long input because the front‑end lacked limits and the database column types were inappropriate.

Pre‑Production Lacks Baseline Test Data

The pre‑production environment did not contain sufficient sample data, hindering later performance testing.

Proposed Improvements

Communicate Fully with the Project Manager : Clarify which environment (test, pre‑production, or production) the requested account belongs to.

Conduct Confirmation Testing in Pre‑Production : After test‑environment success, repeat critical tests (e.g., export functionality) in pre‑production to catch environment‑specific issues.

Confirm Product Requirements : Ensure requirement documents are detailed; for example, specify whether export should include only selected rows or all rows.

Write Comprehensive Test Cases : Include granular steps down to individual buttons and cover abnormal scenarios thoroughly.

Add Baseline Data to Pre‑Production : Populate each module’s list pages with at least eleven records per role to support functional and performance testing.

The author emphasizes that personal absences can affect key milestones and urges proactive communication with all stakeholders to maintain quality.

Finally, the piece encourages testers to learn from these experiences, persist through setbacks, and continuously improve testing practices.