Ankit

• Week 3 - 7 October

Cross-browser Web testing tools

At this thime, there is a huge collection of competing browsers. In this situation, there are no common standards for displaying sites: each one of them may display a site in its own way, for example, by distorting the page content. Due to this fact, the “cross-browser” term emerged, that is the feature of a site to be displayed identically in all browsers.Although the cross-browser issue emerged rather recently, there already exist a great number of tools for testing it.All cross-browser testing tools are different  in the number of supported browsers, ease to use, price, and also testing speed. These factors greatly complicate the choice of the suitable tool.This article is devoted to the problem of choosing the right cross-browser testing tool. It lists the popular tools, their advantages and disadvantages.This article would be useful for testers, who haven’t performed this kind of testing yet, or for people, who face the problem of choosing the suitable tool.BrowserShots gives the possibility to test a site not only in five most popular browsers, but also in less known browsers, such as Netscape, Avant, SeaMonkey.

Ankit Gupta

• Week 2 - 30 September

Analysis of Connection of Options and Input/output Data

It is best to analyze all options in sequence for this purpose. We need to determine the following for each option: what input data it is required for, where it is used, and what types of reports it affects. Common options that depend neither on input data, nor on output data;Input and output data options, which include options that depend on input data and affect final result. For example: The Properties of the included data group of options: a user selects the properties of email messages to be included to a report. I.e. these options affect the final result and depend on input data. In theory, to cover these options completely, we would require to generate all types of reports for each type of database with each option separately. We would also require testing of all possible combinations of options. But first, we need to analyze the influence of input data on each option. As we did earlier, we need to study the inner architecture of the system and discuss the specifics of the inner architecture with developers. This would allow us to determine if we need to test each option with all types of email databases or if testing with one type would be enough. The algorithms for reading the properties from databases are the same for all three types of databases in our example. Thanks to this, we can test options only with one type of database. In much the same way, after studying the inner structure of the system, we determine the degree of dependency of each option on the type of report. In our case, the algorithms for writing each property to a report are the same for all formats of reports, i.e. it is enough to generate one type of report for one type of email database for each option.

Ankit

Week-5

Question

Due to the success of the Watch an Expert series, I was thinking about possibly setting up a bug battle competition in the future, with the ability for uTesters to watch live. I was envisioning it sort of as an eSport, with anywhere from 2-4 testers competing to see who can find the most valuable bugs in a certain amount of time. Although I think this would be a really exciting event, at the same time I'm struggling with whether software testing naturally lends itself to a tournament format. Does anyone think this would be a good idea? Bad idea? Any suggestions on what the rules/entry requirements/judging criteria would be? Anyone interested in participating (assuming it takes place)?

Suggestion:

I really like this idea, and am just going to write out loud for a moment about what I envisioned upon reading your post. Please note that I don't really watch or follow eSport tournaments, so my thoughts might be slightly ill-informed, unrealistic, or just plain bad.When I looked for more information on uTest's previous contests I found this. Unfortunately, many of the links I wanted to click on that branch from that article result in 404s. Have the previous bug battles on uTest been popular? If so, what aspects of the competition did the testers/audience find most appealing? 

I wonder how team dynamics would factor into generating interest for the tester audience. Since testing is (more or less) a solitary effort, what would motivate me to watch Tag-Team Testing? What's the primary value added reason for watching?

Week-4

Five major problem with software quality testing terms.

Maintaining Good Quality Consistently Over Time - How many oeople maintaining the product quality when they add more people in the team product become more challenging. These difference become more impactful because it is now easy to learn and not easy to teach people to test the function in particular way. To pass the function need to be dedicated efforts from leaderwho share his work with everyone in his team.
Centralized knowledge and Expertise - This kind a problem leader will relate better is that the knowledge and expertise on a perticular testing type get centralized to a few people in a team.
Making Work Fun And Intersting - At your work place make a friendly environment not only with your co-worker and also the people working on the top of your. the people i work with them they all are my friends and we go out for couple of hours to hangout. we also help to eachother work.
Work Distribution/Assignment - this is aanother problem if you are working with a large team or Group it will Distribute / Assignment between all of them. this is the best way to work on the lagre assignment in a small part in that way you can get accurate number and right result.
Appreciation and Motivation - when you work and your supervisor check your work he like it. He apperciate and encourage to give you motivation to do more better in your skills.
The conclusion of this article or i just want to say none of us is as smart as all of us!!!