A mandatory process that any software testing company should follow is to provide Sanity Report and Release Notes to the client and stakeholders post-deployment on the live environment.
Sanity report should have information regarding if the list of changes is successfully deployed or not.
It should also document any changes that were planned but were missed....
It depends on the goal of the document. This could differ per industry/company. Maybe a better question would be: "Examples of post-deployment documentation".
Personally I see no need for any post-deployment documentation. Most documentation can be produced before deployment, for example, the changelog which informs users what changes where deployed.
The answer by Muzzamil is excellent, to add it or to make it more simple :
1. Think of why you feel this as a challenge?
Your answer: The answer you stated was that there are too many elements in a single page and finding locator or tests for each element would be hectic or time-consuming
A counter perspective: If it is hard for you to find the locator ...
Nice question, it is.
I had walk through www.fancy.com mobile website. I will try to give you an approach where you will have to just create 4-5 locators for full page test coverage OR to cover all 50 locators and with 1 common function. I will be more practical less theoretical. As I have worked with multiple e-commerce website where you see lots of ...
I'd draw a distinction between two things in this post:
functional testing - you can do it the way you've done it before
UI testing - such a "fancy"/modern/whatever you want to call it should probably be tested in various browsers on both desktop and other devices (tablets, mobile devices, whatnot).
I don't think #2 can be fully automated. Let ...
I would say no. My current project has the QA testing using tests in Python while I code in Java. It is using black-box testing. You may also use JMeter for automated testing, which is coincidentally written in Java.
If you want to use TDD to created automated build tests, then you would have to know C# to be able to integrate the tests into the source ...
If I may be devils advocate, I would suggest sticking with java. If you are the lone automation tester, you can use whatever you want.
Advantages to using java:
Don't need Visual Studio license
Lots more support for Java online
Running into an issue with java ? Chances are, someone else posted a solution online
Most Selenium users code in Java. Then ...
Definetly learn C#. Why?
At Selenium tests level it's basically the same thing as Java 9. With a bit of syntactic sugars. It shouldn't take you more than 2 weeks to get up to speed with C#.
CI/CD and whole infrastructure is set up for dotnet. If you don't want to run this automated tests manually, you will have to either: configure whole infrastructure to ...
Such situations should be addressed both from technical and management perspective, few of the things that needs to addressed are :
1. Does the team consist of only single QA ?
If the team consist of just single QA who would be responsible for the entire automation, then choosing a programming language that is alien to current team will create a dependency....
You can choose any language irrespective of which language is used in development. But it would be better if you go with same programming language which is used in the development, in your case it would be C#/.NET for below reasons:
You can leverage existing libraries used by your team.
Developers can help you out, As you said you will the only person doing ...
One of the biggest mistakes in my career was to pick a different programming language for the test automation than the development team uses.
You won't get help from the development team when you have a programming issue
Developers will probably not run, nor maintain tests as they change the application, you will be maintaining and analysing test results (e....