ALM: Phase 2 - Development

Hey Yall!

I have two things to mention really quickly before diving in to part two of this series:

1. Please take the time to follow me on FB (Charizma Jones), IG (charizmajones) or Twitter (@CaptureMe_TPPB) that we can have further discussion on my articles or so I can hear your perspective on things! You can also email me at

2. It is the last day of the month! I hope you have accomplished most (if not all that you have set your mind to for this month. If you are feeling a little down about not meeting your goals or maybe need a little bit more encouragement for the goals you have in place, head over to Tipsy Tuesday with Tiya and take a look at the great advice she gives concerning New Year Resolution(s).

Last week we touched on the planning phase. Just to give a quick overview, during the planning phase requirement specifications are gathered. It is ideal to have a project manager that can facilitate the project but, in the event, that availability or resources aren’t an option, a list of question should be complied to gather more vital information.

The next phase of this process is the development stage. During this stage if you haven’t already involved all necessary individuals/departments in the planning stage then you want to bring them in at this phase. Departments that you may want to make sure are involved are:

· Marketing

· Sales

· Support

· Development

· Testing

There may be more or less individuals involved but all hands need in on this phase.

The idea is to be able to plan out the technical details as well as the testing needs for the project. Testers need to create all test plans based off the requirement specifications that were given during the planning stage. Developers and Testers will need to work closely together to make sure test cases are validated for the testing phase of the ALM cycle. Test case, according to Software Testing Material should include but needs to be modified to support the project:

· PROJECT NAME: Name of the project the test cases belong to

· MODULE NAME: Name of the module the test cases belong to

· REFERENCE DOCUMENT: Mention the path of the reference documents (if any such as Requirement Document, Test Plan, Test Scenarios etc.,)

· CREATED BY: Name of the Tester who created the test cases

· DATE OF CREATION: When the test cases were created

· REVIEWED BY: Name of the Tester who created the test cases

· DATE OF REVIEW: When the test cases were reviewed

· EXECUTED BY: Name of the Tester who executed the test case

· DATE OF EXECUTION: When the test case was executed

· TEST CASE ID: Each test case should be represented by a unique ID. It’s good practice to follow some naming convention for better understanding and discrimination purpose.

· TEST SCENARIO: Test Scenario ID or title of the test scenario.

· TEST CASE: Title of the test case

· PRE-CONDITION: Conditions which needs to meet before executing the test case.

· TEST STEPS: Mention all the test steps in detail and in the order how it could be executed.

· TEST DATA: The data which could be used an input for the test cases.

· EXPECTED RESULT: The result which we expect once the test cases were executed. It might be anything such as Home Page, Relevant screen, Error message etc.,

· POST-CONDITION: Conditions which needs to achieve when the test case was successfully executed.

· ACTUAL RESULT: The result which system shows once the test case was executed.

· STATUS: If the actual and expected results are same, mention it as Passed. Else make it as Failed. If a test fails, it has to go through the bug life cycle to be fixed.

For the developers, there are many different developmental methodologies that can be practiced, but the main job for a developer is to make sure to create or update all specs documents and any necessary documents needed. This will help during the implementation phase when it is time for the customer to sign off on the overall project.

Keep in mind, that the suggestions and information given just touch the surface of what goes on during the phase. I just want to provide a general overview that can be compared and/or utilized for your own company/agency/ department needs.









3 views0 comments