I am testing a windows application which is very slow but I couldn't figure that out why my application is taking a lot of time while submitting/ saving any form or uploading/ deleting document and editing forms. I need to track by automation that how much time my application is taking for the same with different data and in repetitions.

Any help would be appreciated!

I would suggest you the following things

->Initially gather all the requirements and check with the client if you have any queries through email.

->Document every thing in MOM whenever you have client call and share with everyone who has attended the call(dev team,client,business,QA)

->Prepare a Test Plan strategy document, test cases and share it to client and request him for his sign off.

->Once, you are all set start with smoke testing then check the major functionalities in that release and then could proceed further.

->You could automate the regression test cases as you are going to execute them for every release(I would suggest to use Selenium if its a desktop application then UFT).

Kindly, let me know if you have any queries.

• In-app updates are available only to user accounts that own the app. So, make sure the account you’re using has downloaded your app from Google Play at least once before using the account to test in-app updates.

• Make sure that the app that you are testing in-app updates with has the same application ID and is signed with the same signing key as the one available from Google Play.

• Because Google Play can only update an app to a higher version code, make sure the app you are testing as a lower version code than the update version code.

• Make sure the account is eligible and the Google Play cache is up to date. To do so, while logged into the Google Play Store account on the test device, proceed as follows:

1. Make sure you completely close the Google Play Store App.
2. Open the Google Play Store app and go to the My Apps & Games tab.
3. If the app you are testing doesn’t appear with an available update, check that you’ve properly set up your testing tracks.

What could be the reasons for taking more time while doing automation testing than manual testing for testing specific feature for example?

List of Software Test Estimation Techniques you can use:

• Work Breakdown Structure
• 3-Point Software Testing Estimation Technique
• Wideband Delphi technique
• Function Point/Testing Point Analysis
• Use – Case Point Method
• Percentage distribution
• Ad-hoc method

In a long-standing project written in symfony 3, test coverage is zero. Now this obviously leads to a lot of mistakes and ruins life.
How can you quickly cover a large project with tests and what would you do in such a situation?
Perhaps someone had cases of taking a project out of such a deplorable state into a project state from which one does not want to quit.