Hey, Nasr is here! I've been supporting startups in different fields for almost 3 years+. I am glad now to get my experiences published here through giving a hand. Unit tests is a vital step through the development process and it needs a continuous sync between design & business & dev (if available). Since this is a painful step, I can provide assistance with writing unit tests for your application.
For the best achievable results, software reusability should be available. I can assist also with building that in case if it is not there. Technical debt is always a monster that eats and demolishes the future of any startup. Let's get it done!
Packages Provided: ------------------------
Plug & Play: This is a straight forward package. Its purpose is to add the unit tests directly to your code base, assuming that the code is already is following one of the design principles. Business logic and any possible information will be valuable before we jump into the code
Tiny Refactor This package should take care of refactoring/creating components and reusability along with creating unit tests to enhance compilation performance, work load on main browser thread, lighthouse results and more…
Legacy This package is literally a lifesaver! The old code will be examined really carefully and valued based on the latest design patterns, then we decide for either a refactor or a rebuild. The hardest phase will be in the first couple of weeks as we need all the possible business information that could help redefine/reshape the software structure to be a future proof, maintainable, reliable, plugin-able and flexible. Everything should take its time perfectly. We may need the following practices: - Re-analyze the UX/UI design system - Check if there is any modifications or updates on the design - Prepare mind maps, documents, sketches and discuss ideas - Convert the design into persistence model through these exercises (list entities - define relations - build a persistence model system) - Mind map tech stack, including possible future needed 3rd parties. - Setup project source code, automation hooks, Github Continuous Integration, Wiki and technical documentation - Setup Action plans, checklists - Build (Atom - Molecule - Organism) component system with TDD approach and add component documentation for developers and reviewers - Setup POCs if needed To ensure the best outputs to fight against high technical debts, we may need some or all of the points mentioned above.
Let's make sure that we contact before purchasing any package.
Still have
questions?
Can’t find the answer you’re looking for? Please send me a message.
Extra revision
$100
Service Packages
Legacy
$18000
5 x
revisions
Your app needs a full refactor or a rebuild along with building unit tests.
This package is literally a lifesaver! The old code will be examined really carefully and valued based on the latest design patterns, then we decide for either a refactor or a rebuild. The hardest phase will be in the first couple of weeks as we need all the possible business information that could help redefine/reshape the software structure to be a future proof, maintainable, reliable, plugin-able and flexible. Everything should take its time perfectly. We may need the following practices:
- Re-analyze the UX/UI design system
- Check if there is any modifications or updates on the design
- Prepare mind maps, documents, sketches and discuss ideas
- Convert the design into persistence model through these exercises (list entities - define relations - build a persistence model system)
- Mind map tech stack, including possible future needed 3rd parties.
- Setup project source code, automation hooks, Github Continuous Integration, Wiki and technical documentation
- Setup Action plans, checklists
- Build (Atom - Molecule - Organism) component system with TDD approach and add component documentation for developers and reviewers
- Setup POCs if needed
To ensure the best outputs to fight against high technical debts, we may need some or all of the points mentioned above.
Your code needs reusability to be fulfilled along with building unit tests for it.
This package should take care of refactoring/creating components and reusability along with creating unit tests to enhance compilation performance, work load on main browser thread, lighthouse results and more…
Unit tests will be added if your code is well organized.
This is a straight forward package. Its purpose is to add the unit tests directly to your code base, assuming that the code is already is following one of the design principles. Business logic and any possible information will be valuable before we jump into the code
Your app needs a full refactor or a rebuild along with building unit tests.
This package is literally a lifesaver! The old code will be examined really carefully and valued based on the latest design patterns, then we decide for either a refactor or a rebuild. The hardest phase will be in the first couple of weeks as we need all the possible business information that could help redefine/reshape the software structure to be a future proof, maintainable, reliable, plugin-able and flexible. Everything should take its time perfectly. We may need the following practices:
- Re-analyze the UX/UI design system
- Check if there is any modifications or updates on the design
- Prepare mind maps, documents, sketches and discuss ideas
- Convert the design into persistence model through these exercises (list entities - define relations - build a persistence model system)
- Mind map tech stack, including possible future needed 3rd parties.
- Setup project source code, automation hooks, Github Continuous Integration, Wiki and technical documentation
- Setup Action plans, checklists
- Build (Atom - Molecule - Organism) component system with TDD approach and add component documentation for developers and reviewers
- Setup POCs if needed
To ensure the best outputs to fight against high technical debts, we may need some or all of the points mentioned above.
Your code needs reusability to be fulfilled along with building unit tests for it.
This package should take care of refactoring/creating components and reusability along with creating unit tests to enhance compilation performance, work load on main browser thread, lighthouse results and more…
Unit tests will be added if your code is well organized.
This is a straight forward package. Its purpose is to add the unit tests directly to your code base, assuming that the code is already is following one of the design principles. Business logic and any possible information will be valuable before we jump into the code