Diving into QA

Fiddler is a free and open-source packet analyzer. It is used for network troubleshooting, analysis, software, communications protocol development and education. Fiddler captures HTTP and HTTPS traffic data between the browser and server. These data are extremely valuable to troubleshoot HTTP, Java script errors and performance issues related to browser page rendering, this article is a step by step tutorial to guide how to use Fiddler and capture HTTP Traffic.

Performance testing measures response times across various system layers, and identifies potential bottlenecks that may exist. Ideally, the system being tested is already functionally stable. Load testing is often a part of the larger performance testing strategy. It is different from performance testing, in that performance testing may measure response time with a single user exercising the system or with multiple users exercising the system. Load testing, however, focusing on increasing the load on the system to some stated or implied maximum load , to verified the system can handled defined system boundaries. Volume testing is often considered synonymous with load testing, yet volume testing focuses on data. Stress testing goes to the next level with respect to the quantity of users or data place in the system. The intent is to go beyond testing stated or implied boundaries, and identify actual boundaries by identifying the precise load at which the system breaks (its resources...

Selenium Grid manual Also, good wiki from Google

I was asked many times about front-end testing: what to test and how to test it, and what tool are best to be used? And this is my final answer: You need to consider Mike Cohn’s analogy – the test pyramid. It will help you decide what kind of testing best to be done in a certain situation. At the bottom of the pyramid are the solid test units they are the foundation of the test strategy – they can provide you with a fast feedback. At the top, occupying the smallest part of the pyramid , are the UI tests. They interact with your UI directly(for example Selenium), but are costly and very slow on feedback. They can become very brittle and hard to maintain. At the middle of the pyramid there are integration tests that do not require an UI. In Rails, for instance, you would test your REST interface directly instead of interacting with the DOM elements. For smoke or regression tests UI are very useful. If there is a need to automate these, there are some dangers to consider. First, you shoul...

For test email app sometimes good to have a group with numbers of faked emails. Was done for 'contacts' (addressbook/surveymonkey.com). Script posted for help young QA engineers.

Because Python Is Easy to Use: A simple program written in C++, C, Java and Python. All program prints "Hello world".

Firebug is a free web development tool. In this tutorial we are going to discuss following - How to install Firebug. Inspect and edit HTML with Firebug. Inspect and edit CSS with Firebug. Debug and profile JavaScript with Firebug. Execute JavaScript on the fly with Firebug. Logging for JavaScript with Firebug. Monitor network activity with Firebug. Installing Firebug

REST & HTTP API developer's pocket knife. Easy to use and configurable. HATEOAS, Hypermedia, Requests History+Repository, and more.

What Is Agile? The Agile movement proposes alternatives to traditional project management. Agile approaches are typically used in software development to help businesses respond to unpredictability.

Based by my experience, "Overplay" is one of the best app for test internalization billing for your business. Download, install and enjoy your tests.

I think this is a best explanation: Reporting a new bug or feature request 1. Title: A short one-sentence summary that explains the problem (not your suggested solution). 2. Assigned to: 3. CC: 4. Priority: 5. Severity: 6. Description: 6.a. Full details of the issue, giving as much detail as possible. This can include: 6.b. Steps to Reproduce: 6.c. Actual Results: 6.d. Expected Result: 6.e. For feature requests: A description of what you would like to achieve, and why. A user story is an effective way of conveying this. 6.f. Please also provide any other information that might be useful, such as: the web browsers, computer systems you've seen the bug on; To attach a log file or screenshot (but make sure that no confidential data is included or shown), click the Upload File button (a cloud with an arrow) in the toolbar of the Description field. Software has bugs, yes, even ours. Since programmers are human, and humans make mistakes, ergo bugs. When you come across a bug in our softw...

1. git pull # transfer latest build 2. git status # file(build, branch) Status 3. git add . # add all to git ( or git add ) 3. git commit –a –m ‘comment’ # comment about push or changes inside a code 4. git push -u origin master # push latest build or latest changes to server few other commands: git diff # branch changes git branch –v # branch git add test/login/ initializing git config –global –list

Akamai Mobitest is a free tool created to raise awareness to Mobile Web Performance. Your page is loaded on a real mobile device, and you'll receive rich detail about how long it took to load, including waterfall charts and video recording of the page load. The Mobitest agent has been open-sourced, so you can install it on your own devices, connected to your own WebPageTest private instance. The site provides an option to compare the history of tests. Use this URL Enter your mobile website in the space provided for website URL. Choose type of your device. Specify how many runs. Choose Location. Run Performance Test and know the results for your mobile website!

  Levels: 1 Unit testing 2 Integration testing 3 System testing 4 Acceptance testing Testing Types: 1 Installation testing 2 Compatibility testing 3 Smoke and sanity testing 4 Regression testing 5 Acceptance testing 6 Alpha testing 7 Beta testing 8 Functional vs non-functional testing 9 Destructive testing 10 Software performance testing 11 Usability testing 12 Accessibility 13 Security testing 14 Internationalization and localization 15 Development testing 16 Performance 17 Load 18 Stress

ssh root@199.198.3.0 Connect to remote host. ssh -v root@199.198.3.0 Look at the number of ssh build. sudo su or sudo -s Super User Doing permit. sudo dhclient Releasing and updating my machine IP address. sudo /etc/init.d/networking restart Restart all network settings. scp /home//examples.desktop root@122.223.55.2:/home... Copy between local and remote host scp root@(IP address - where file located):/home.... /home (local path to folder) Copy file from remote host to local machine ifconfig See machine's IP address $ touch /home//123 'touch' - created file ls -all /home//123 Check file owner and permissions sudo chown -R root:root /home/fallenangel/123 'chown' - change owner wget https://www.test.com/logo4w.png wget - download file from URL tar -cf logo.tar logo4w.png Archive file tar -xf logo.tar Open archived file (if user located in a same directory) top what applications used over memory kill process # hit "k" and choose a "PID" number. MAC-...

Selenium Webdriver provides two types of waits – implicit & explicit. An explicit wait makes WebDriver to wait for a certain condition to occur before proceeding further with executions. An implicit wait makes WebDriver to poll the DOM for a certain amount of time when trying to locate an element. Full information ### Explicit Waits ### ”’ An explicit waits is code you define to wait for a certain condition to occur before proceeding further in the code. The worst case of this is time.sleep(), which sets the condition to an exact time period to wait. There are some convenience methods provided that help you write code that will wait only as long as required. WebDriverWait in combination with ExpectedCondition is one way this can be accomplished. from selenium.webdriver.support import expected_conditions as EC ”’ wait = WebDriverWait(driver, 10) element = wait.until(EC.element_to_be_clickable((By.ID,’someid’))) ### Implicit Waits ### ”’ An implicit wait is to tell WebDriver to po...

A Back end is the engine of any client/server system. If the back end malfunctions, it may cause system deadlock, data corruption, data loss and bad performance. Many front ends log on to a single SQL server. A bug in a back end may put serious impact on the whole system. Too many bugs in a back end will cost tremendous resources to find and fix bugs and delay the system developments.