zodman

RSS

libbitcoin the other implementation of bitcoin

http://libbitcoin.dyne.org/

ppa

https://wiki.unsystem.net/index.php/Debian_packaging

lets go to the party!

  • <zodman> [13:26:44] too silent here :S
  • <caedes> [14:16:37] zodman the party is on git :)
Apr 9

curl -s localhost:8000/api/v1/ | python -m json.tool

- json prettify

Apr 1
Ok  esta imagen represeta cuando encuentras de donde viene el bug que llevas mas de una semana buscandolo y te das cuenta que era una coma en el js.

Ok esta imagen represeta cuando encuentras de donde viene el bug que llevas mas de una semana buscandolo y te das cuenta que era una coma en el js.

the deployment

thecodinglove:

image

/* by arekibian */

GettingStarted - js-test-driver - Getting Started with JsTestDriver - Remote javascript console - Google Project Hosting

JavaScript Module Pattern: In-Depth

Mar 7

How to write good Test Cases

Every tester writes test cases however many times the test cases are rejected by reviewers because of bad quality, in order to write good test cases one should know what are the characteristics of a good test case.

A good test case has certain characteristics which are:

  1. Should be accurate and tests what it is intended to test.
  2. No unnecessary steps should be included in it.
  3. It should be reusable.
  4. It should be traceable to requirements.
  5. It should be compliant to regulations.
  6. It should be independent i.e. You should be able to execute it in any order without any dependency on other test cases.
  7. It should be simple and clear, any tester should be able to understand it by reading once.
  8. Now keeping in mind these characteristics you can write good and effective test cases.

TIPS for writing good test cases

Tests only one thing

Always make sure that your test case tests only one thing, if you try to test multiple conditions in one test case it becomes very difficult to track results and errors.

Organize your test cases consistently

You can organize your test cases in many ways however you should always follow the same pattern to organize you test cases.

Write independent test cases

Your test cases should not have dependency on other test cases, i.e you should be able to execute your test case individually with having dependency on other test cases.

Write small test cases

Always mention purpose of each test case clearly in test case.

- http://www.softwaretestingmentor.com/tptc/writing-good-test-cases/

Mar 6

Varnish Cheat Sheet

Get the top request methods

varnishtop -i RxRequest
Top URLS that missed the cache.

varnishtop -i TxURL
Top URLS that HIT the cache.

varnishtop -i RxURL
All URLs that hit the cache in real time.

varnishlog -o VCL_call hit | grep RxURL
All URLs that MISSED the cache in real time

varnishlog -i TxURL
Look at an incoming client request of a specific URL:

varnishlog -c -o RxURL index.html
Look at a a backend request of a specific URL:

varnishlog -b -o TxURL index.html
See requests for one specific Hostname:

varnishlog -c -o RxHeader “Host: cirrii.com”
See the age of the cache objects for a specific hostname:

varnishlog -c -o RxHeader “Host: cirrii.com” | grep Age

- http://pegmanm.tumblr.com/post/11097673680/varnish-cheat-sheet

★ Your Daily Photo on Facebook | Facebook