Development & Testing Process
Harsh
Jitesh
Morgan
In order to make the UAT process more efficient and improve the communication between our two teams we would like to suggest some refinements to our workflow in Target Process.
Development Comment Requirements
Purpose:
To ensure Testing & UAT knows what exactly has been developed from start to finish and what is unable or dependant on other cards. Should we need to, this will help us identify cards to split for later development/Testing and make progress more efficient.
Process:
- When development is complete, leave a comment with the following information;
- Acceptance Criteria Fully Implemented:[COPY PASTE AC AS THEY APPEAR IN THE CARD IN TARGET PROCESS]
- Acceptance Criteria Not Implemented: [COPY PASTE AC AS THEY APPEAR IN THE CARD IN TARGET PROCESS]
- Notes about the user Story:[LIST changes to AC’s that may have occurred due to meetings talks, development restraints or bug fixes]
- QA on both DEVIt and Industrial side should not proceed without this.
- If a card is might need splitting the product owners (Industrial) will make this determination
DevIT Testing Comment Requirements:
Purpose
To ensure the FULLY developed acceptance criteria are testable and ready for QA and UAT.
Process:
- Before DevIT starts the QA round, ensure the development comment described above is present.
- After DevIT has completed the QA round, leave a comment with the following information;
- Tested by:[Name of Tester]
- Tested on:[Browser & OS Type]
- Bugs found during Testing:[Number of Bugs]
- Tests that were Executed:[Acceptance Criteria only? Ad-hok? Exploration? Only AC’s 1,2,3]
- Notes:[Any info that might affect UAT results or Acceptance Criteria]
- Once QA has finished, the AC’s listed as fully implemented have been tested and a comment is added with the above information, place it in UAT.
Our hope is that by following this process, we can ensure that all requirements will be met in the final product and that progress can be made more efficiently. It is imperative that the cards coming through to UAT are as close as possible to done in order to meet the deadline and that any user story that is not complete has been clearly captured.
We can discuss further on Thursday's call and are open to any other suggestions to improve this process.
Mel
Thanks,
Morgan
The defined process is fine from our side also. but We are suggesting before start any story we should discuss about story requirement and do clear each and every points mentioned in user story by call. It will reduce rework and bugs from our side.
We are agree with
like,
mentioned all points but we are need to mentioned only Acceptance Criteria Not Implemented.
DevIT Testing comment requirements looks good. Please provide your feedback.
Following are names and emails of team members.
1, Shrinivas Sambhare <Shrinivas.Sambhare@devitpl.com>
2, Janak Thakkar <Janak.Thakkar@devitpl.com>
3, Anil Mori <Anil.Mori@devitpl.com>
4, Piyush Rathod <Piyush.Rathod@devitpl.com>
5, Jignesh Suthar <Jignesh.Suthar@devitpl.com>
6, Jaykishan Vaghela <Jaykishan.Vaghela@devitpl.com>
7, Ayushi Patel <Ayushi.Patel@devitpl.com>
8, Piyush Kanpariya <Piyush.Kanpariya@devitpl.com>
9, Hiren Patel <Hiren.Patel@devitpl.com>
10, Darsh Shah <Darsh.Shah@devitpl.com> (QA)
11, Jitesh Dhuravala
12, Harsh Parikh
13, Ketan Sondarva <Ketan.Sondarva@devitpl.com> (TPM)
Thanks,
Jitesh
In the meantime,
Morgan
I've added Ketan to the meeting invite and Basecamp projects. I'll will work on getting access to Target Process for those who don't have it yet.
Savannah
Also,
Thanks,
Morgan
Also, although I may not attend the call every week, could you please add me to the calendar invite.
Thanks,
Morgan
There are so many bugs & suggestions in ISLG are completed but meanwhile, new stories development of Dispute Document, Treaties and Arbitration Rules (Multiple Language, Grouping, Primary) and Tagging issue are in progress.
Hence, we will publish new version of ISLG admin side on 19th February on rebuild.islg.
Hope this is fine.
Did this get resolved this morning? Are we going to publish a new version of ISLG on the 19th?
Thanks,
Morgan
We did discuss this approach but cautioned that this will severely hinder our UAT progress and would likely prevent us from meeting deadlines.
We will need to have features released to as more consistently.
Mel
A reminder to send the revised list of employees who require access to Target Process.
CC
I think only two new users needed on Target Process Account.
- Ketan Sondarva (ketan.sondarva@devitpl.com)
- Darsh Shah (darsh.shah@devitpl.com)
Thanks,
Ketan
I am still not able to see ISLG Subscriber stories in my TargetProcess. The Old ISLG Subscriber Login and Registration stories are displayed under ISLG Subscriber.
Please do needful.
Morgan
Following are my credentials of Target Process.
User Name : harsh.parikh@devitpl.com
Password : 05041990
Your account is fixed. The issue was that the wrong project was checked:
Modifying this controls what cards are fed to the project's board and display. I've checked on the proper board and it should work now:
Just in case this happens in the future so you know how to solve it!
Savannah
cc
the two accounts have been added:
usernames & temporary passwords:
Ketan.Sondarva
DevIT2020
Darsh.Shah
DevIT2020
Following up on our discussion yesterday about the scheduled 19th release for ISLG, did you have a chance to discuss internally on how to deal with this?
Also,
Also, do we need to create a similar schedule for ILG?
Thanks,
Morgan
Yes
Morgan
After discussion with Team, we have planned to release ISLG Admin section in two phases. 1st phase will be released on 12th Feb, 2020 as per below attached excel sheet and 2nd phase will be on 19th Feb, 2020 with all left issues and pending stories of ISLG Admin.
Also, I have attached here the list of tasks/bugs in excel sheet for your reference of 1st phase which will be updated on Target Process by 12th Feb.
Thanks
Ketan
Morgan
Can you please review again the process described above re: documentation for testing and UAT.
We are still missing comments and updates on cards in UAT and these would be helpful given that we have a number of different resources conducting UAT. Any decisions made re: implementation and/or changes should be recorded to avoid duplication of bugs and inconsistency throughout the application.
Thank you for your help with this.
Mel
To reiterate
Thanks,
Morgan
Already discussed with Jitesh, Harsh & team and they are aware about the process to follow now onwards making sure that each card will be updated according to process developed by Mel.
Thanks,
Ketan
It has come to my attention while reviewing the latest release for this UAT period that the cards have NOT followed the requested comments on testing and development as outlined and agreed upon above.
This is extremely critical to us, to ensure we are not wasting time on cards untested and not fully developed so can hit this deadline. This process should be done for every card that is in UAT; bug, card, task anything that will land on our team to give the final rounds of QA (UAT).
I will reiterate the process here from the original post:
DevIT Testing Comment Requirements:
Purpose
To ensure the FULLY developed acceptance criteria are testable and ready for QA and UAT.
Process:
Please confirm this will be updated and implemented on all current and future cards. We have asked your team of this for the past month for every release and is still undone. If you need an example I can write one out how it should appear.
William
I am in process of making this practice smoother as finalized in last status call with Mogran & Team. But there is a constraint from our end as we have to finish testing of all stories in given timeline for both ISLG & ILG. We have only one QA working on all 100's of stories to understand & test as per acceptance criteria. We have put developers' comment in relevant cards whenever it required.
Today we have discussed with Mel on today's call on this and we have also concern regarding the same to implement it thoroughly on all stories which we put in UAT. For this we have arranged one more resource in QA from our side to help our QC Darsh Shah and he will start helping him from this mid week.
Still we can specifically assign our QA to comment as per defined testing process and will update you by end of tomorrow.
Thanks
Ketan
We have finished QA comments on all strories of ISLG Admin side. please review and let us know for any query.
Thanks,
Ketan
Thank you for adding the comments and details, its much appreciated. We took some time to review the comments today and its looking pretty complete.
With that said, there is a concern of note and confusion that a series of cards have been set to UAT but have not in fact been fixed or tested. Since the team has been focusing on bug regressions at the moment, the main stories are just being looked at now, and have already been seeing discrepancies between whats listed as 'fully tested' and whats been actually done before landing on our plate in 'UAT'. I have posted some examples below.
Storys
13108
Bugs
14510 14047 14063 14101 14396 14515
Can you let us know what happened with these? My worry now is that the comments have been added without regard for what was actually completed in an effort to meet our request OR comments were added to the incorrect cards and were moved before being ready for UAT. The notes on many cards seem pretty detailed, however seeing a story like 13108 has me worried its a tip of the iceberg.
Thank you Ketan,
William
Actually, There was some misunderstanding between Developer & QC. The QC was checked the criteria only developed items but he was missed to mentioned in comment.
In story no. 13108, There is some confusion and we are going to discuss on tomorrow's call with Melisa.
For the bugs, The QC doesn't mentioned the comment in bugs due to time constraint. But, Now will take care this is in future and we also put comments in all bug cards.