• Part 5: System Development Life Cycle – Release Planning and Deployment
    Permalink

    Part 5: System Development Life Cycle – Release Planning and Deployment

Part 5: System Development Life Cycle – Release Planning and Deployment

The Release Planning and Deployment stage begins upon completion of software testing. During this time, no changes to the software are permitted excepting those explicitly directed by the Customer. Release Planning and Deployment is performed in three phases: Pre-deployment, Deployment, and Post-deployment

Pre-Deployment

The Pre-Deployment Phase addresses three major tasks simultaneously:

Release Planning
Training and Documentation
User Acceptance Testing (UAT)

In most cases, software deployments to the System Users will be transparent to end users.

However, careful release planning and coordination is essential for ensuring that the Customer is consulted on all new or altered code and the decision to release it. Release planning also includes identification of active and standby resources, as well as specification of a roll-back strategy in the event it becomes necessary to revert or roll back the deployed code.

Partnet will collaborate with the Customer and any associated Change Control Board (CCB) representatives to create a release deployment plan, to include:

A cutover schedule, identifying the date and time for the release.
A listing of the features and/or problem reports that will be contained in the release.
Identification of a release coordinator.
A release impact assessment, including impacts to integration partners.
A roll-back plan, outlining a contingency process for removing new changes should it become necessary.

The following tasks can then be performed as part of the pre-deployment phase:

Identify the deployment team, including: Release Project Manager, Change/Configuration Manager, Database Administrator, Technical Lead, Software Test Engineer, End User Tester
Prepare a draft deployment schedule which:

Chronologically outlines required deployment tasks and estimates, including tasks to be performed by external third parties.
Identifies the complexity, timeframe, and task owner of each deployment task.

Execute a mock deployment on the Staging environment, which allows the team to rehearse deployment tasks and validate estimates.
Execute the roll-back plan on the Staging environment […]

  • Part 4: Software Development Life Cycle - Software Development, Testing, and Quality Assurance
    Permalink

    Part 4: Software Development Life Cycle – Software Development, Testing, and Quality Assurance

Part 4: Software Development Life Cycle – Software Development, Testing, and Quality Assurance

Agile best practices recommend overlapping development and testing cycles. This helps identify and resolve software defects early, while minimizing scenarios where developers are simultaneously trying to fix old bugs and build new features.

Overlapping development and testing cycles also promotes the incremental delivery of working code. This process allows new features and bug fixes to be rapidly promoted, while allowing the Customer to review new features as they are developed, and make decisions about when specific features are ultimately deployed to Production.

Partnet’s software development process is enhanced by the incorporation of continuous delivery methodologies. Continuous delivery is a collection of techniques designed to improve and automate software delivery. These techniques include:

Continuous delivery pipeline
Automated testing
Mainline development
Continuous integration

Continuous delivery allows software to be developed to a high standard, easily packaged, and rapidly deployed to the various environments. Additionally, new features and bug fixes can be rapidly promoted to the Production environment with minimal risk and overhead.

Our developers use a continuous delivery pipeline to implement continuous delivery principles.

The deployment pipeline is like an automated assembly line which the code passes through to ensure it is ready for Production. This assembly line includes:

Building the software
Running unit tests
Building the application deployment
Running automated User-Interface (UI) tests

This method allows functional software to be rapidly promoted to non-Production environments for Customer inspection; or promoted directly to Production in cases where a feature or bug fix is immediately required.  For projects employing the Scrum process, this cycle repeats within each sprint until the Product Owner signifies all requirements have been met and the feature is Production-ready

Automated Testing

Automated testing requires close interaction between software developers and test engineers. The following process is employed within each development cycle (Scrum or Kanban):

Test engineers write test outline(s) for […]

  • SeAuto_PressRelease
    Permalink Gallery

    Partnet Proudly Introduces SeAuto: Test Automation Framework

Partnet Proudly Introduces SeAuto: Test Automation Framework

Partnet Enters the Automated Testing Market with their Open Source Automated Testing Software, SeAuto
Create a robust, browser-based test automation framework with a single command.

SALT LAKE CITY – March 31, 2015

Partnet, Inc. announced today the worldwide release of SeAuto (http://se-auto.com), a robust, open source software testing tool that integrates Selenium’s browser automation with test frameworks. SeAuto combines the best in pre-built and configuration ease to automate testing on multiple browsers and operating systems, including Windows, Mac OS, and Linux to bring users to the next level in automated testing.

Partnet CEO, Don Brown is pleased with the offering and with the results that they’ve seen thus far.

“Our pre-built Selenium Auto Test Framework can save years of effort by avoiding framework development and costly ‘trial-and-error’ in selecting products and creating tests,” said Brown.

Doug Erickson, Director of Software Development at Partnet agrees, noting that “Partnet developed SeAuto to help our testers focus on creating tests, rather than running the tests.” Erickson added, “SeAuto makes it easy to include browser-based testing in a continuous integration (CI) pipeline and enables developers to run these tests before checking in code; that gives better, faster results. It’s our hope that others will find the same value in this effort to bridge the gap between their favorite test framework and Selenium.”
Customization and Integration
SeAuto was created for software testers looking for a pre-built, automated test tool that’s ready-to-go with little setup required (http://www.partnet.com/seauto). Partnet equipped SeAuto to be easily integrated with any CI and with the ability to test on any major browser and operating system.

“SeAuto takes the guesswork and experimentation time out of building a test automation framework, has lower maintenance overhead, and is far more robust than GUI-based, “point-and-click” automation tools,” […]

Google+