Yavor Kirov YavorK

## Exercise.md

      
              4 files
            
          
              0 forks
            
          
                0 comments
              
            
              1 star
            
          
                YavorK
                / Exercise.md
            
            
              Created
              November 14, 2025 13:04
                — forked from purrarri/Exercise.md
            
              
                Q2. Breakdown test cases as in cucumber/ gherkin formatting as for assesment : Mention all necessary fields which should be included in a bug.
              
          
    Q2 Go to https://petstore.octoperf.com/actions/Catalog.action and report at
least 3 bugs.
Bug Report in Gherkin/Cucumber Format

This document serves as a bug report in Gherkin/Cucumber format for reporting an identified issue in the system. The bug report follows the structured format of Gherkin to provide clear details about the bug and its expected behavior.
Usage

The bug report is written using the Gherkin syntax, which allows for easy understanding and communication between stakeholders, developers, and testers. Each bug report includes the following information:

  
## index.html
<!DOCTYPE html>
<html>

<head>
  <title>Hello Page</title>
  <script src="https://unpkg.com/htmx.org@1.9.2"></script>
</head>

<body>
  <h1>Hello</h1>

## sse.html
<html>
<body>
<div id="result"></div>
<script>
if (typeof(EventSource) !== 'undefined') {
    console.info('Starting connection...');
    var source = new EventSource('/stream.php');
    source.addEventListener('open', function(e) {
        console.info('Connection was opened.');
    }, false);

## service-workers.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                YavorK
                / service-workers.md
            
            
              Created
              October 3, 2018 14:52
                — forked from Rich-Harris/service-workers.md
            
              
                Stuff I wish I'd known sooner about service workers
              
          
    Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Use Canary for development instead of Chrome stable

Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.

  
## debug.php
// PHP < 5.3.6
foreach (debug_backtrace() as $trace)
{
	echo sprintf("\n%s:%s %s::%s", $trace['file'], $trace['line'], $trace['class'], $trace['function']);
}
die;

// PHP >= 5.3.6
debug_print_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);
die;
	<!DOCTYPE html>
	<html>

	<head>
	<title>Hello Page</title>
	<script src="https://unpkg.com/htmx.org@1.9.2"></script>
	</head>

	<body>
	<h1>Hello</h1>
	<html>
	<body>
	<div id="result"></div>
	<script>
	if (typeof(EventSource) !== 'undefined') {
	console.info('Starting connection...');
	var source = new EventSource('/stream.php');
	source.addEventListener('open', function(e) {
	console.info('Connection was opened.');
	}, false);
	// PHP < 5.3.6
	foreach (debug_backtrace() as $trace)
	{
	echo sprintf("\n%s:%s %s::%s", $trace['file'], $trace['line'], $trace['class'], $trace['function']);
	}
	die;

	// PHP >= 5.3.6
	debug_print_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);
	die;