-
Notifications
You must be signed in to change notification settings - Fork 0
Notes regarding "testing environment"
Mohamed Hassan (JOHN) edited this page Jan 26, 2025
·
14 revisions
Deconstruct the testing environment
upon moving and stabilization in production environment
and going live.
The bare metal of testing environment
should be cleaned and maintained for future projects after that.
Draw connectors between those components according to your plan.
- Frontend (WEB and MOBILE)
- Proxy
- RS-x, RS-y, ...
- SJ-x, SJ-y, ...
- MB
- DS
Where RS is defined as a REST API service that represents some sort of business activity
Where SJ is defined as a Scheduled Job that represents some sort of business activity
Where MB is defined as a message-broker that can hold n of queues
Where DS is defined as a data storage that utilizes a relational-database
- Overview
- University Role
- Architectural Components
- Legal and Ethical Development Specialization
- System Administration
- Software Deployment
- Git Repositories | Access Control
- Testing notes - Tester [QA]
- Daily Standups
- Onboarding process upon hiring newcomers
- Tickets Flow AKA Industrial Software Manufacturing Process
- Sprint
- Legal and Ethical Aspects of Contracts
- Maintenance Deals: new contracts after delivery to avoid wasting the money of the clients and burning out the human resources
- Human Resources Planning to the Software-Development-Unit
- Possible future moves of Human resources
- Notes to Managerial Positions
- Notes for Self Study During the University Phase
- Screening Interviews
- Search keywords for recruiters
- Email-Writing
- Job advertising template for recruiters
- Ethics of writing useful software
- How to do a complaint against someone in a safe way
- Internal and external communication tools within an organization
- Necessary amount of information technology knowledge for employees before work