Webqualitelogicielle.com

Expert Qualité logicielle

Consultant expert qualité logicielle, performance et organisation du SI. Formateur expérimenté.

Contact: M.Sangaré mohamed@sangare.eu ou au 0668331696

CV 2013

Formation à distance par WebEx à la qualité logicielle,aux tests, à QTP,QC,ALM

 
 
 
 
  
 
 

Dernire

 
 
 
 
Date: 30 Mars 2009
Catgorie: Testing chez Google
 
 
 
 
 
 
 
Date: 30 Mars 2009
Catgorie: Testing chez Google
 
 
 
 
 
 
 
http://chris.pirillo.com/ - Here\'s why I\'m \"upgrading\" from Windows Vista to Windows XP in a few days. I just flipped on the webcam and started talking - it\'s all based on a post I made to my personal blog the other day. Are you on Vista? Are you still on XP? What are your plans?
Date: 13 Mars 2009
Catgorie: Tests et humour
 
 
 
 
 
 
 
http://AppleenEspañol.com For the New York Times, David Pogue reviews Windows Vista, trying to prove in his video that \"Microsoft did not steal ideas from Mac OS X.\" Apple en Español http://AppleenEspañol.com apple iphone mac os x tiger leopard ipod imac macbook pro itunes quicktime steve jobs ilife get a nano español safari [Plus d'informations] [Moins d'informations]
Date: 13 Mars 2009
Catgorie: Tests et humour
 
 
 
 
 
 
 
Credits to scrubadub (check for user: scrubadub1 for more videos like this !) for sharing this first, until he got banned... Here we go again... Please don\'t ban me.
Date: 13 Mars 2009
Catgorie: Tests logiciels
 
 
 
 
 
 
 
http://www.softwaretestingvideos.com/blog/ \"Visit for FREE Complete Video Training\" Get Software testing Jobs just watching these Videos.Bug life cycle helps you understand the whole process involved in defect reporting.Testers are hired to find bugs & you need to know what happens when a bug in a software application is found. In software development process, the bug has a life cycle. The bug should go through the life cycle to be closed. A specific life cycle ensures that the process is standardized. The bug attains different states in the life cycle. The life cycle of the bug can be shown diagrammatically as follows: The different states of a bug can be summarized as follows: 1. New 2. Open 3. Assign 4. Test 5. Verified 6. Deferred 7. Reopened 8. Duplicate 9. Rejected and 10. Closed Description of Various Stages: 1. New: When the bug is posted for the first time, its state will be \"NEW\". This means that the bug is not yet approved. 2. Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as \"OPEN\". 3. Assign: Once the lead changes the state as \"OPEN\", he assigns the bug to corresponding developer or developer team. The state of the bug now is changed to \"ASSIGN\". 4. Test: Once the developer fixes the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to \"TEST\". It specifies that the bug has been fixed and is released to testing team. 5. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software. 6. Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to \"REJECTED\". 7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to \"DUPLICATE\". 8. Verified: Once the bug is fixed and the status is changed to \"TEST\", the tester tests the bug. If the bug is not present in the software, he approves that the bug is fixed and changes the status to \"VERIFIED\". 9. Reopened: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to \"REOPENED\". The bug traverses the life cycle once again. 10. Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to \"CLOSED\". This state means that the bug is fixed, tested and approved. While defect prevention is much more effective and efficient in reducing the number of defects, most organization conducts defect discovery and removal. Discovering and removing defects is an expensive and inefficient process. It is much more efficient for an organization to conduct activities that prevent defects. Guidelines on deciding the Severity of Bug: Indicate the impact each defect has on testing efforts or users and administrators of the application under test. This information is used by developers and management as the basis for assigning priority of work on defects. A sample guideline for assignment of Priority Levels during the product test phase includes: 1. Critical / Show Stopper — An item that prevents further testing of the product or function under test can be classified as Critical Bug. No workaround is possible for such bugs. Examples of this include a missing menu option or security permission required to access a function under test. 2. Major / High — A defect that does not function as expected/designed or cause other functionality to fail to meet requirements can be classified as Major Bug. The workaround can be provided for such bugs. Examples of this include inaccurate calculations; the wrong field being updated, etc. 3. Average / Medium — The defects which do not conform to standards and conventions can be classified as Medium Bugs. Easy workarounds exists to achieve functionality objectives. Examples include matching visual and text links which lead to different end points. 4. Minor / Low — Cosmetic defects which does not affect the functionality of the system can be classified as Minor Bugs. [Plus d'informations] [Moins d'informations]
Date: 13 Mars 2009
Catgorie: Tests logiciels
 
 
 
 
 
 
 
Lecture Series on Software Engineering by Prof.N.L. Sarda, Prof. Umesh Bellur,Prof.R.K.Joshi and Prof.Shashi Kelkar, Department of Computer Science & Engineering ,IIT Bombay . For more details on NPTEL visit http://nptel.iitm.ac.in
Date: 13 Mars 2009
Catgorie: Tests logiciels
 
 
 
 
 
 
 
Jonathan Kohl and Michael Bolton at the STAREAST 2008 Conference in Orlando, Fla. See more videos like this at cmcrossroads.com & agilejournal.com
Date: 13 Mars 2009
Catgorie: Tests et humour
 
 
 
Plus regards

 
 
 
 
http://www.softwaretestingvideos.com/blog/ \"Visit for FREE complete video training\" Get Software Testing Jobs just watching these Videos A test plan is a systematic approach to testing a system such as a machine or software. The plan typically contains a detailed understanding of what the eventual workflow will be. In software testing, a test plan gives detailed testing information regarding an upcoming testing effort, including * Scope of testing. * Schedule. * Test Deliverables. * Release Criteria. * Risks and Contingencies. [Plus d'informations] [Moins d'informations]
Date: 13 Mars 2009
Catgorie: Tests logiciels
 
 
 
 
 
 
 
Software Testing Tutorial
Date: 13 Mars 2009
Catgorie: Tests logiciels
 
 
 
 
 
 
 
Software testing is a challenge, but for uTest it\'s a unique challenge. The uTest platform makes it easy to build a truly global software testing team using a community driven approach. But how does uTest test its own software? CEO Doron Reuveni answers that question and describes how uTest is its own customer. All of the uTest platform is tested by a global community of testers across multiple browser and environments. [Plus d'informations] [Moins d'informations]
Date: 26 Février 2009
Catgorie:
 
 
 
 
 
 
 
Date: 30 Mars 2009
Catgorie: Testing chez Google
 
 
 
 
 
 
 
http://www.softwaretestingvideos.com/blog/ \"Visit for FREE Complete Video Training\" Get Software testing Jobs just watching these Videos.Bug life cycle helps you understand the whole process involved in defect reporting.Testers are hired to find bugs & you need to know what happens when a bug in a software application is found. In software development process, the bug has a life cycle. The bug should go through the life cycle to be closed. A specific life cycle ensures that the process is standardized. The bug attains different states in the life cycle. The life cycle of the bug can be shown diagrammatically as follows: The different states of a bug can be summarized as follows: 1. New 2. Open 3. Assign 4. Test 5. Verified 6. Deferred 7. Reopened 8. Duplicate 9. Rejected and 10. Closed Description of Various Stages: 1. New: When the bug is posted for the first time, its state will be \"NEW\". This means that the bug is not yet approved. 2. Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as \"OPEN\". 3. Assign: Once the lead changes the state as \"OPEN\", he assigns the bug to corresponding developer or developer team. The state of the bug now is changed to \"ASSIGN\". 4. Test: Once the developer fixes the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to \"TEST\". It specifies that the bug has been fixed and is released to testing team. 5. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software. 6. Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to \"REJECTED\". 7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to \"DUPLICATE\". 8. Verified: Once the bug is fixed and the status is changed to \"TEST\", the tester tests the bug. If the bug is not present in the software, he approves that the bug is fixed and changes the status to \"VERIFIED\". 9. Reopened: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to \"REOPENED\". The bug traverses the life cycle once again. 10. Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to \"CLOSED\". This state means that the bug is fixed, tested and approved. While defect prevention is much more effective and efficient in reducing the number of defects, most organization conducts defect discovery and removal. Discovering and removing defects is an expensive and inefficient process. It is much more efficient for an organization to conduct activities that prevent defects. Guidelines on deciding the Severity of Bug: Indicate the impact each defect has on testing efforts or users and administrators of the application under test. This information is used by developers and management as the basis for assigning priority of work on defects. A sample guideline for assignment of Priority Levels during the product test phase includes: 1. Critical / Show Stopper — An item that prevents further testing of the product or function under test can be classified as Critical Bug. No workaround is possible for such bugs. Examples of this include a missing menu option or security permission required to access a function under test. 2. Major / High — A defect that does not function as expected/designed or cause other functionality to fail to meet requirements can be classified as Major Bug. The workaround can be provided for such bugs. Examples of this include inaccurate calculations; the wrong field being updated, etc. 3. Average / Medium — The defects which do not conform to standards and conventions can be classified as Medium Bugs. Easy workarounds exists to achieve functionality objectives. Examples include matching visual and text links which lead to different end points. 4. Minor / Low — Cosmetic defects which does not affect the functionality of the system can be classified as Minor Bugs. [Plus d'informations] [Moins d'informations]
Date: 13 Mars 2009
Catgorie: Tests logiciels
 
 
 
 
 
 
 
Jonathan Kohl and Michael Bolton at the STAREAST 2008 Conference in Orlando, Fla. See more videos like this at cmcrossroads.com & agilejournal.com
Date: 13 Mars 2009
Catgorie: Tests et humour
 
 
 
 
 
 
 
Date: 30 Mars 2009
Catgorie: Testing chez Google
 
 
 
 
 
 
 
Lecture Series on Software Engineering by Prof.N.L. Sarda, Prof. Umesh Bellur,Prof.R.K.Joshi and Prof.Shashi Kelkar, Department of Computer Science & Engineering ,IIT Bombay . For more details on NPTEL visit http://nptel.iitm.ac.in
Date: 13 Mars 2009
Catgorie: Tests logiciels
 
 
 
Meilleures notes

Description

Catgories

 
 
 
 
Automatisation des tests
 
 
 
 
 
 
 
Les vidéos testing chez Google
 
 
 
 
 
 
 
Tests et humour
 
 
 
 
 
 
 
Vidéos sur le test logiciel
 
 
 

Google Ads

#Qualité Twitter

Liens publicitaires