Novice2Professional

SCRUM FRAMEWORK - Roles, Activities, and Artifacts Agile Static, cumbersome software is no longer an option for competitive companies; it’s critical to develop processes that quickly iterate new code and release new features while simultaneously ensuring high quality. As a result, many companies have turned to Agile development methodology, which focuses on fast iterations and constant evaluation to produce flexible, robust and stable software. But understanding the value of Agile doesn’t guarantee easy adoption — adapting traditional QA processes to an Agile environment is not something you learn from a book, but a skill and culture developed through experience. Teams converting to agile have challenges not only in adapting processes and thinking differently, but also behaving differently. XBOSoft offers a unique blend of software testing expertise in development methodologies from waterfall to hybrid to Agile. Our depth of hands-on experience in a variety of industries gives us ...

How does Fiddler work? Understanding the background Fiddler sits between HTTP client and server and listens on a port. It acts as man-in-the-middle   proxy.When using fiddler, the requests is being sent directly   to Fiddler proxy   bridge, Fiddler will forward the request to real server, Likewise,   the response from server is also sent to the fiddler, fiddler will forward it to the browser. To the client browser, Fiddler claims to be the web server, and to the web server, Fiddler mimics the web browser. In this process, Fiddler intercepts and records all the incoming and outgoing  messages. What’s Fiddler used for? Troubleshooting issues in your web application Security testing Performance evaluations Debugging web traffic from most computers and devices Commonly used Tabs in Fiddler   Web Sessions   Session Inspector   Statistics Tab [Performance evaluation]  ...

      Test management using Microsoft Test Manager [Novice to Advanced] Basic Level Users: An overview on the basic usage of Microsoft Test manager can be achieved by following the Video links shared below, listed with 4 videos to give complete insights into the basic usage. Novice understanding of Microsoft Test Manager Advanced Level Users: Please follow the links below to understand how to Run tests with MTM & Visual Studio Web Portal 1.  Testing your application using Microsoft Test Manager 2.  Test on a lab environment Diagnostic Data Adapters: Changing how Developers and Testers work together  The Test Impact Analysis using Test Impact Collector While you are testing your application, Microsoft Test Manager can collect data that will help diagnose any fault that you might find. If you create a bug report while you’re testing, the data is automatically attached to the bug work item. You can decide what kinds...

Prevention is Better than Cure An Old medicine in a New bottle Felt like sharing few lines from a book "Software Testing with Visual Studio by Jeff Levinson" which i came across while reading it, which went in sync with my thoughts which cab be implemented as best approach to cut down the no of the bugs in any Software development process before releasing it to Testing team. "Developers need to produce code with fewer defects (contrary to popular belief, bugs in functionality are not the sole province of the developer; they are usually nurtured in the requirements phase) and testers need to provide better information to developers to help them run down bugs in the application" lines quoted from the book.  My concise was that more Bugs detected were not because the Developers lack good coding skills but due to the case that requirements were not pretty much transparent or due to lack of visibility on how the f...

                        Speaking about Agile planning & management with Agile tools like TFS, VS & MTM leads us specifically to Scrum, where in we concentrate on the below items First of all lets see the hierarchy of Work Items followed in Scrum process. Workflow states Agile process comparison: Workflow states define how a work item progresses upon its creation to closure. For example, the four main states defined for the User Story (Agile process) define a progression of four states, from New, Active, Resolved, to Closed. (The Removed state supports removing a work item from appearing on the backlog; to learn more, see Move, change, or delete work items.) The natural progressions and regressions of the user story, product backlog item, and requirement WITs are as shown. Roles in Agile Scrum Under Work Tab we can see backlog, board & work Items. we will discuss whats the impo...