User talk:Abhinavvaid
From Wikipedia, the free encyclopedia
[edit] Art Of Effective Software Testing -- Wireless Systems
How do we define the Quality, how do we measure it, across what do we measure it. How do we know that the testing is complete and the product has reached the stability to be shipped to the market.
Best Practices What does it take to build the best Test Organization An Organization, wherein the End to End Testing derives the production best practices and design to implementation/deployment and post deployment support
The Jargon Associated and Meanings with respect to our Work
What is Testing: A lot of people associated with IT still say that Testing is a pretty new field. I have a friend and an ex-colleague who had started www.whatistesting.com 6 years back when we were working together.
The way I would define it is to dig out the system, tryin to simulate it exactly as the deployment scenario, communicate effectively everything with respect to the Software Under Test, based on Methodologies being used.
The dictionary meaning bug/defect is often used to refer to a problem or fault in the Software under Test.
What does it take to build the best Test Organization.
Attitude Conviction Killing instinct to dig out and deliver
Culture Passion towards testing and cutting edge technologies Work towards technology, sharing and learning Power of Ethics
What we do with respect to Software Testing
Building silicon with ARM based Architecture. We are known for a good expertise on low power embedded technologies Building drivers, putting on OS, building an image on top of it. Writing the device driver
Testing the device driver
Developement, UT, Sanity Testing, Engineering Testing, Conformance Testing, CM Release
Wireless network support followed by Product Release.
[edit] IMPORTANCE WITH RESPECT TO OUR WORK
Priority and Severity states and trade-offs between them: Mapping to our jargon Blocker and Crasher.
Release Blockers: Last Severity 1 but 1st priority/BLOCKER (from our perspective):
Examples of Extreme Cases:
Has anyone come across a Microsoft Product which specifies "Win" instead of "Windows, but you won't be able to find it. Why, because as a Tester you might be logging it as a last severity, but for the Vendor/Microsoft it becomes priority 1/BLOCKER.
Examples of Extreme Cases: S 1 but last priority: Crash
Test Blockers: Is a typical case in which you log the crash bug(Blocker), but it is taken as a last priority by the management. Why???
In one of the instances, a vendor had released a version of OS, which specified that after installing the OS on a new machine, pull out the cable to the HDD and the OS will crash and would be completely un-recoverable. The only workaround would be required to re-install the entire OS again. Still the vendor released the OS with this as a known bug, Why? Because the vendor would not expect the end user to do it.
[edit] Effective Execution and Reporting
Importance of Logs
Importance of logging with respect to not logging.
What happens when you find a crash the re-produceability of the bug is 1 % and it takes 1 day to simulate the bug, what do you do? In case you leave it, and the customer finds it. Trust me guys, you are fired. The best resolution to this typical scenario is: log the bug with a note that the reproduceability of bug is 1 %, and try to provide maximum logs, so that respective developer can point out at the exact location as to where the exception occured without actually spending time to simulate the same.
Some fun time:
Reporting all passes and sending the report without actually executing the tests. The product getting backfired from the customer premises. The industry does not spare mistakes, and this one can be worst.
Importance of Testing Templates and Documentation:
Test Plan/ Test Case
Automation: What takes it to implement.
The Road Ahead:
There was a time when the "Notepad" was being used to write java code, then saving .java files and compiling etc. I actually used to do it. Later when I saw code generating wizards, I thanked God that I was not a tester.
Importance of testing.
With respect to everything mentioned above, I would be putting in templates/documents etc and link it to this place so that everyone can have a look and provide appropriate feedback.
Other activities which are often associated with software testing are:
Static Analysis: Static analysis involves stepping through the source code without actually executing the code.
Dynamic Analysis: Dynamic Analysis involves looking at the behaviour of software under test, at the time of execution.
Test plan
Purpose To prescribe the scope, approach, resources, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with this plan.
Test Case Identifiers Test items: This includes:
Features to be tested;
Features not to be tested; This is all the more important which people generally ignore
Item pass/fail criteria
Test deliverables
Testing Methodologies
Schedules & milestones; Risks Associated
Testing Related Documentation
Requirement Specs User Guide Operations guide Installation guide Troubleshooting guide There can be other's also based on specific requirements,
Features to be tested Identify all software features and combinations of software features to be tested. Identify the test design speciÞcation associated with each feature and each combination of features.
Features not to be tested This is equally important & I have often observed that people generally avoid/ignore this part & end up embarassment.
A couple of url's that could prove handy: http://en.wikipedia.org/wiki/Software_testing
http://en.wikipedia.org/wiki/Scenario_test
http://en.wikipedia.org/wiki/Test_suite
http://en.wikipedia.org/wiki/Software_engineering
http://en.wikipedia.org/wiki/Test_script
http://en.wikipedia.org/wiki/Regression_testing
www.stickyminds.com
www.whatistesting.com
www.scriptinganswers.com
www.sqa-tester.com
www.indiantestingboard.org
www.indyacellular.in: A book released under Open source and downloadable from "www.indyacellular.in". Demonstration of Project Automation using 10 different Programming languages/tools/technologies
[edit] Pure Testing Test Automation: MOM and Updates
Updates as on December 26, 2007
[edit] Image copyright problem with Image:QTP Overview-Ankit-december28-07.pdf
Thank you for uploading Image:QTP Overview-Ankit-december28-07.pdf. However, it currently is missing information on its copyright status. Wikipedia takes copyright very seriously. It may be deleted soon, unless we can determine the license and the source of the image. If you know this information, then you can add a copyright tag to the image description page.
If you have any questions, please feel free to ask them at the media copyright questions page. Thanks again for your cooperation. —Remember the dot (talk) 08:16, 27 December 2007 (UTC)
[edit] License tagging for Image:MOM-Performance&Automation-26Dec07.sxw
Thanks for uploading Image:MOM-Performance&Automation-26Dec07.sxw. You don't seem to have indicated the license status of the image. Wikipedia uses a set of image copyright tags to indicate this information; to add a tag to the image, select the appropriate tag from this list, click on this link, then click "Edit this page" and add the tag to the image's description. If there doesn't seem to be a suitable tag, the image is probably not appropriate for use on Wikipedia.
For help in choosing the correct tag, or for any other questions, leave a message on Wikipedia:Media copyright questions. Thank you for your cooperation. --ImageTaggingBot (talk) 09:07, 2 January 2008 (UTC)
[edit] Image copyright problem with Image:Evaluating qtp for test automation.sxw
Thank you for uploading Image:Evaluating qtp for test automation.sxw. However, it currently is missing information on its copyright status. Wikipedia takes copyright very seriously. It may be deleted soon, unless we can determine the license and the source of the image. If you know this information, then you can add a copyright tag to the image description page.
If you have any questions, please feel free to ask them at the media copyright questions page. Thanks again for your cooperation. NOTE: once you correct this, please remove the tag from the image's page. STBotI (talk) 12:06, 9 January 2008 (UTC)
[edit] Image copyright problem with Image:Using QTP for Automating Yahoo Messenger.pdf
Thank you for uploading Image:Using QTP for Automating Yahoo Messenger.pdf. However, it currently is missing information on its copyright status. Wikipedia takes copyright very seriously. It may be deleted soon, unless we can determine the license and the source of the image. If you know this information, then you can add a copyright tag to the image description page.
If you have any questions, please feel free to ask them at the media copyright questions page. Thanks again for your cooperation. NOTE: once you correct this, please remove the tag from the image's page. STBotI (talk) 11:23, 30 January 2008 (UTC)
[edit] The latest in Agile Development Models
There was once a Quality Meeting I was attending (10 years back) with almost 25 people gathering in a big conference room. In the middle of the Meeting a guy just stood up midway and there came very high pitch tone "You guys talk about quality, quality, and then one day you have a quality meeting and that's the end of quality).
I could never ever forget that.
One of the biggest challenges that one faces when evolving technologies are also being incorporated/penetrated (worst case).
is the technical jargon that's associated which stumps everyone with me as the first one on the list. And it was always the same, right from early Microsoft COM days to where we stand today admist technical revolution. COM was just a common platform (set of guidelines that were primarily promoted by Microsoft) to be used across the developer community to come to a common platform and talk/interface/build/test and so on.
Agile is another term, and the latest non-bookish example is the aggressively changing/demanding customer base and cut-throat competition (irrespective of the technological) domain.
Non Bookish Confession: I have seen examples from the embedded devices to very very large scale enterprise apps. Each one transforming/fine-tuning the model as per their needs.
[edit] Image copyright problem with Image:MOM-Performance&Automation-26Dec07.sxw
Thank you for uploading Image:MOM-Performance&Automation-26Dec07.sxw. However, it currently is missing information on its copyright status. Wikipedia takes copyright very seriously. It may be deleted soon, unless we can determine the license and the source of the image. If you know this information, then you can add a copyright tag to the image description page.
If you have any questions, please feel free to ask them at the media copyright questions page. Thanks again for your cooperation. Shinerunner (talk) 11:20, 24 February 2008 (UTC)
