Hello,
If you are an Appium tester and want to showcase your skills, here is an amazing opportunity for you! MOZARK’s online global app testing contest- QAppathon is now live!
The contest is free to register, all you need to do is:
- Sign up to MOZARK QAppAssure
- Write an Appium script to measure the Home page load time of your app.
- Run the script on at least 10 devices across the QAppAssure device cloud.
- Ensure a minimum of 50 test runs.
- Send in the logs and a brief description of your test methodology to [email protected]
The first 10 testers to successfully complete the challenge will get an Amazon gift voucher worth INR 5k and MOZARK cloud vouchers worth INR 10k!
Register Now and be a MOZARK certified Appium tester.
First of all you need to know your capacity based on size of your team. Then about story points, It is a relative term and does not directly co-relate to actual hours. Since story points have no relevance to actual hours, it makes it easy for scrum teams to think abstract about the effort required to complete a story.
But how do you know which story is a 3 and which is a five? In order to do that each team would have to find a baseline story. It does not have to be the smallest one, but one that all in the team can relate too. From then on all sizing should be done compared to that baseline. This also creates a lot of confusion as most scrum masters who come from a PMP background relate this immediately to hours. Story points do not relate to hours. So lets just not compare them. There is another technique called ideal hours which can be used.
That is soul of scrum learn and adapt iteratively.