Skip to main content

Ghost Inspector Introduction

What is Ghost Inspector ? Why we use it ?


Ghost-Inspector Tutorial


Hello Friends,
Soft-Qa me aap sabhi ka Swagat hai,
Aaaj se mai ek mai ek tutorial start kr rha hu  jisme aap logo ko Ghost Inspector tools ke bare be btaunga ki ye tools hota kya hai aur kyu use karte hai software automation testing me.

Ye hindi language me hai, and English me mai jald hi start karunga,

Aaplogo se request hai ki yadi aaplog hamare channel pr new hai to IS Chanel Ko Jarur Subscribe Kr le taki aapko Is tutorial ki notification milti rahe aur aap is tutorial se kuchh sikh sake aur aap apne resume me new technology ke bare me add on ke sake .

Ab start karte hai, ghostispector hota kya hai




What is Ghost Inspector ?


GhostInspector ek automated website testing and monitoring tool hai jo hamare Application or Website ke issues ko check karne me help karta hai.

GhostInspector website ya application ko  Chrome ya firefor browser me thik usi tarah se check karta hai jaise hm manual kisi application ko check karte hai.

Ghostinsepctor pr website ko automate karne ke liye, aapko sabse pehle GhostInspector je site pr jake Signup karna padega.

Test create karne ke liye, aapko Test Recorder aapke browser me install karna padega,
Test recorder Install hone ke bad, aapko login karna padega, uske baad aap website ko Automate kr sakte hai.

How to set Auto Run Schedule:


Aap is tools pr easily apne test ke liye auto run- schedule , notification set kr sakte hai.
Isme easily automatically log generate hota hai, aapko kuch karne ki jarurat nhi hai.

Ye ek Paid Tool hai isliye aapko iska plan buy karna padega but ye aapko learning purpose se 14 days ke trial account provide karta hai.
Aap is trial account se GhostInspector pr website automate karna Easily sikh sakte hai.
Yeh bahut hi easy tools hai and koi bhi ise asani sikh sakta hai.
Watch video on youtube and Subscribe my channel:-





Comments

Popular posts from this blog

How to analyze a JMeter summary report?

  A  Jmeter  Test Plan must have listener to showcase the result of performance test execution. Listeners capture the response coming back from Server while Jmeter runs and showcase in the form of – tree, tables, graphs and log files. It also allows you to save the result in a file for future reference. There are many types of listeners Jmeter provides. Some of them are: Summary Report, Aggregate Report, Aggregate Graph, View Results Tree, View Results in Table etc. Here is the detailed understanding of each parameter in Summary report. By referring to the figure: Label : It is the name/URL for the specific HTTP(s) Request. If you have selected “Include group name in label?” option then the name of the Thread Group is applied as the prefix to each label. Samples : This indicates the number of virtual users per request. Average : It is the average time taken by all the samples to execute specific label. In our case, the average time for Label 1 is 942 milliseconds & to...

What is Error, Bug and Defec ?

What is Error, Bug and Defect in software testing ? Error :- When developer compile a program and program compilation is failed due to some syntax problem or not used correct logic, is called an Error.  For example:-  public class  { public static void main( string []args) { s.o.p(" hello") } } Now after running this program, we will get an error because there is syntax issues as we haven't use correct syntax to print output. Bug : Bug is something that is not producing expected output or something is not behaving as expected.  For example- Developer develop a program to add two number and that program is running fine but producing wrong result. public class  { public static void main( string []args) { int a=3; int b=2; int s= ++a+b; System.out.println(" hello"); } } Actual output: 6 Expected outpit: 5 So here system is not producing expected output after adding two number. In simple term, whe...

How to write useful end-to-end tests with Cypress

  Visit YouTube Channel to watch more riting software of any complexity can often be a messy task, and this only gets worse when teams get larger and more people start to work on the same codebase. This problem is worsened in frontend development, where there are so many moving parts that writing unit and functional tests might not be enough to verify the application’s correctness. For example, you can’t really verify that a particular user flow doesn’t cause issues through a unit test. End-to-end testing  allows you to replicate user behavior on your application and verify that everything works as it should. If you’re writing production-grade web apps, writing e2e tests is a no-brainer. In this article, we’ll take a look at how to write useful e2e tests on the frontend using  Cypress . While there are other e2e testing tools like  Selenium  and  Nightwatch.js , we’ll focus on Cypress because of its suite of features, which include time traveling through yo...