Let me provide some test cases for different type of testing with a common example. Hope it will help those who like to know about test cases. Let us consider yahoo mail as an example. We are on the log in page and want to test that.
Our functional test cases can include:
1-Check the character lenght of User ID and Password fields
2- When a User enters three false entries in user ID and password field, then a alert mesage should come
3-The login window should be in the right hand side of the screen
4-whether user can enter his User ID and password in more than one system
5-Forgot password and help options should be there in login window.
6-When a user enters invalid user ID and password. An alert message should come
our performance test cases can include:
1-Check the response time when the yahoo mail window open in your system.
2-When a user enters a valid user ID and password , check the response time.
3-When a user enters invalid user ID and password,check the response time.
Our load testing test cases can include:
1- When more than one user enters the same user ID and password in different systems , check the response time.
2-check the reponse time form the server when a number of user hits the Yahoo mail server.
Our Stress testing test cases can include:
1- When more than one user enters the same user ID and password in different systems , check the response time.
Our security testing test cases can include:
1-Check for the SSL certificate when the user enters a valid user ID and password.
2- check for the "https " address for secure login
3-For three invalid entries in user ID and password , there should be an alert message.
Hope this will help to understand about test cases. I will post a formal test case example for other testers convenience, in future.
November 22, 2007
I Managed to pass ISEB
Hi mates,
sorry for the delay in posting. I had been busy reading for the ISEB certification in software testing. By god's grace I passed the exam with considerable percentage. That is the main reason for not posting anything so far. From today onwards i will try my best to post on daily basis..
chenththuran
sorry for the delay in posting. I had been busy reading for the ISEB certification in software testing. By god's grace I passed the exam with considerable percentage. That is the main reason for not posting anything so far. From today onwards i will try my best to post on daily basis..
chenththuran
October 18, 2007
Something for today
finally i managed to get a day off tomorrow. Thought to watch some technical clips in youtube.I found Google posted these videos from their 2nd Annual GTAC - Google Test Automation Conference.
Some of the most difficult challenges in creating great software are guaranteeing it works every time, for every customer, ensuring that it will scale well, and making it accessible to all users. Languages have become easier to deal with over the years. Intergrated development environments have made developers life ease. However, I feel that automation techniques and easy to use test tools lagged behind.I totally accept that there are excellent solutions for automated testing, still there is room for innovation.
Google Test Automation Conference held on Aug 2007 address many of these issues. Hey folk! have a look of these nice videos. Here the link for you
www.youtube.com/view_play_list?p=7D3E685B59779C16
Watch, enjoy, and have a little fun
Some of the most difficult challenges in creating great software are guaranteeing it works every time, for every customer, ensuring that it will scale well, and making it accessible to all users. Languages have become easier to deal with over the years. Intergrated development environments have made developers life ease. However, I feel that automation techniques and easy to use test tools lagged behind.I totally accept that there are excellent solutions for automated testing, still there is room for innovation.
Google Test Automation Conference held on Aug 2007 address many of these issues. Hey folk! have a look of these nice videos. Here the link for you
www.youtube.com/view_play_list?p=7D3E685B59779C16
Watch, enjoy, and have a little fun
October 08, 2007
what makes good leadership and what makes bad leadership in relation to 'quality'?
well,my friend pointed out leadership as a type of ''Quality''. According to his view there are many different ways to understand leadership and many different perspectives from which to define or describe it so it is generally contextual. He defines Leadership as the art of influencing others to their maximum performance to accomplish tasks, objectives, and projects.
In general, a leader is interpreted as someone who sets direction in an effort and influences people to follow that direction. How they set that direction and influence people gets into the operational definitions based on context. For example, a good leader displays degrees of focus, unclouded vision, ability to adapt readily to varied demands and novel situations, etc.
It pays to realize that there are also different types of leadership models that can be applied within QA - or any organization. For example, the current popular one is situational leadership. Another is collaborative leadership. Yet another is process leadership. Another one that is making the rounds lately is thought-leadership.
In order to understand the full spectrum on the view of leadership, I propose a definition, which certainly is in bad taste, but is the one that many leaders end up following.
Leadership: The activity by which one seeks to maintain their leadership position by objectifying their team to their superiors and assuming credit for the positive results of the team.
There are many reasons this pattern is exhibited, not all of them are because of selfishness or arrogance.
In general, a leader is interpreted as someone who sets direction in an effort and influences people to follow that direction. How they set that direction and influence people gets into the operational definitions based on context. For example, a good leader displays degrees of focus, unclouded vision, ability to adapt readily to varied demands and novel situations, etc.
It pays to realize that there are also different types of leadership models that can be applied within QA - or any organization. For example, the current popular one is situational leadership. Another is collaborative leadership. Yet another is process leadership. Another one that is making the rounds lately is thought-leadership.
In order to understand the full spectrum on the view of leadership, I propose a definition, which certainly is in bad taste, but is the one that many leaders end up following.
Leadership: The activity by which one seeks to maintain their leadership position by objectifying their team to their superiors and assuming credit for the positive results of the team.
There are many reasons this pattern is exhibited, not all of them are because of selfishness or arrogance.
The Day Best Practices Died
When reading the above titled article in the web recently, i came across this quote.
''Even though BP's are good for any project, the applicability and usability of the same should be carefully analyzed in order to maintain the sanctitiy of the principles and methodologies''
If the applicability and usability needs to be analyzed, then its not a "best" practice. There are good practices in context, but there really is no such thing as a "best" practice that can be applied regardless of context."Best Practices" that work in one context are regularly applied in contexts that they don't fit. This seems to be the opposite of what Deming advocated. Deming sought to find the best ways of doing specific things in specific contexts. The most efficient methods and tools for one context may be different than those for another.
The specifics of any task -- including the people -- have an impact on what might be best.
Instead of finding good practices for specific contexts, software development and testing (and IT in general) practices are often taken out of context and applied as a one size fits all "best" practice.
Much of what masquerades as "best practices" are really vendor practices that lead to selling tools and services. I am especially skeptical of any vendor-sponsored best practice.
''Even though BP's are good for any project, the applicability and usability of the same should be carefully analyzed in order to maintain the sanctitiy of the principles and methodologies''
If the applicability and usability needs to be analyzed, then its not a "best" practice. There are good practices in context, but there really is no such thing as a "best" practice that can be applied regardless of context."Best Practices" that work in one context are regularly applied in contexts that they don't fit. This seems to be the opposite of what Deming advocated. Deming sought to find the best ways of doing specific things in specific contexts. The most efficient methods and tools for one context may be different than those for another.
The specifics of any task -- including the people -- have an impact on what might be best.
Instead of finding good practices for specific contexts, software development and testing (and IT in general) practices are often taken out of context and applied as a one size fits all "best" practice.
Much of what masquerades as "best practices" are really vendor practices that lead to selling tools and services. I am especially skeptical of any vendor-sponsored best practice.
Subscribe to:
Posts (Atom)
Posts
