Software delivery in a timely planned manner has been of utmost priority for the software development organization. The new changes to the release schedule can cause further delays in the release causing frustration for end users. As a whole the goal of the software development is to keep the customer base happy but doing so gets difficult as there is no endpoint of introducing new changes in the release to meet the expectations of end users. This causes more expense in software development and delays the schedule of future releases in software development. Our approach is to introduce a generic template of release cadence using test early methodology to support the execution of web browser-based tasks framework. The approach consists of various factors i.e. Time, quality of developed software and timely release which ensures that the release has a hard commit date and at a certain point introducing new changes in the software risks the associated components of feature under development and AUT (application under test).

错误:搜索内容不能为空,请输入英文关键词
错误:关键词超出字数限制,请精简
高级检索

Development of Deployment Schedule for Web Browser Based Tasks Framework Using Release Cadence Approach Based on Test Early Methodology

  • Nagendra Singh Yadav,
  • Vishal Kumar Goar

摘要

Software delivery in a timely planned manner has been of utmost priority for the software development organization. The new changes to the release schedule can cause further delays in the release causing frustration for end users. As a whole the goal of the software development is to keep the customer base happy but doing so gets difficult as there is no endpoint of introducing new changes in the release to meet the expectations of end users. This causes more expense in software development and delays the schedule of future releases in software development. Our approach is to introduce a generic template of release cadence using test early methodology to support the execution of web browser-based tasks framework. The approach consists of various factors i.e. Time, quality of developed software and timely release which ensures that the release has a hard commit date and at a certain point introducing new changes in the software risks the associated components of feature under development and AUT (application under test).