Scribd
Upload
25 views1 page

Developing Multiple Projects

When developing multiple projects simultaneously, integration testing is essential to merge code without conflicts. A more complex process may include user-acceptance testing and a staging environment to ensure smooth production deployment. It is recommended to make all fixes in a development organization and follow a repeatable process for migrating changes to production.

Uploaded by

hitu4u
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
25 views1 page

Developing Multiple Projects

When developing multiple projects simultaneously, integration testing is essential to merge code without conflicts. A more complex process may include user-acceptance testing and a staging environment to ensure smooth production deployment. It is recommended to make all fixes in a development organization and follow a repeatable process for migrating changes to production.

Uploaded by

hitu4u
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

Developing Multiple Projects with Integration, Testing, and Staging If you have multiple developers and more than

one project in development that wi ll be released at the same time, you need integration testing to make sure that the separate code lines can be merged with out conflict. In the future, you might want to include user-acceptance testing (UAT) to determine if the original design requir ements are met. A more elaborate development process can also contain a staging environment where you ensure that the deploym ent to production goes exactly as planned. In such a development scenario, you might wonder where to make changes to the co de line. If a feature fails any test on the way towards production deployment, do you fix the feature in the organization wh ere it failed, or start the entire process over again? As the complexity of your application development process increases, you will find that fixing things as you go is not a good model. Instead, you will want to make all fixes in a development organizati on and follow a repeatable process for migrating that change toward production. The following image depicts this process:

You might also like