Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Jun 22, 2018 3:54 PM
Replying to Mayte Mata Sivera
...
Only one additional note: UAT isn't training, sometimes users forget that :)
Very important and almost always the cause of contention. You cannot conduct UAT if you do not know the system but people are resistant to be trained on a system not yet accepted. Irrespective of how you solve the conundrum users should know how to use functionality in order to test it. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Personally I try to avoid software tools during the actual testing. I have always found it to be distracting. Maybe I've just never found the right tool ;) Saving Changes...
Great contributions. In the telecoms industry here in Nigeria where I work, UAT is done manually, we have a template we fill, we check, error per sec, severe error, receive signal level and alot of stuffs. The range of this values might vary because every project is unique. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Oct 09, 2018 3:50 AM
Replying to Mohamad El Maraachli
...
this is very useful , do you have a certain template that would allow us to better document the process of the UAT and the scenarios tested
All the documents I could provide are property of the company where I am working today. But you can find a lot into the internet. I am in charge to create those documents then my recommendation is going to the IEEE standards where you can find models about documents, beyond as I mentioned there are lot of templates into the internet. Saving Changes...
I am a Business PM. Does anyone have a good UAT template to share. Heck, I'd even take a bad template at this point (no viruses, please).
I"m a newbie to UAT - what exactly are "scripts"?
Josephine -
Are you looking for a UAT strategy, plan or actual test cases? Have you checked the template section of this site?
I'd interpret scripts as being actual test scripts being run as part of the execution of one or more UAT test cases.
Kiron Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
We use HP ALM (Application Life Cycle Management) . We have found it to be extremely useful in documenting Test Cases and Executing them. It also provides Traceability to user Requirements . The pre and post sign off on the test cases and execution respectively is electronic and this tool integrates with Active Directory.
I recommend this to anyone working in a highly regulated environment who requires visibility of their test execution.
The Onus is on the business users to execute the UAT but Test Managers and Test Analysts can guide them on the proper use of the tool and also help create their test cases and hold their hands during execution.
...
1 reply by Sergio Luis Conte
Dec 05, 2019 5:59 PM
Sergio Luis Conte
...
We use it too.
Saving Changes...
Jacqueline PattersonSr IT Project Manager| Cuyahoga CountyShaker Heights, Oh, United States
Does anyone have a UAT template, please? Saving Changes...
Karl TwortSenior Project Manager| Fresh EggUnited Kingdom
It's not only about making sure the software works, but also making sure it doesn't break.
Might sound like the same thing but actually very different. Using structured test scripts to ensure that the functionality works as expected and also scenarios where you specifically design tests to make sure logic, business rules, validation etc are not failing.
Tools such as Jira, Trello etc can enable you to manage each test, using a KanBan board to move cards through the various stages and statuses of the test phase. Saving Changes...
Lonnie PacelliAuthor & President| ProjectManagementAdvisor.comBellevue, Wa, United States
One of the rules I employ is all UAT test conditions must be run during systems integration testing first. A good UAT isn't about finding new issues; it's about building confidence amongst users that the solution is ready to be used. Saving Changes...